/usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f7f44720740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007fc934ea4740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007fc1f24d7740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f690ff0c740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f6eb7273740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007fc3137c5740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007fdadf106740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f42abf3c740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f3ff0171740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f36e5a27740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f510a2ec740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f3132a3b740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: User: command not found /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: User: command not found /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: User: command not found /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: User: command not found /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: User: command not found /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: User: command not found /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f9e15303740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f31afe30740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f1d2113b740 (most recent call first): /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 8: cd: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11: No such file or directory /usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/set_env_vars.py: No such file or directory Python path configuration: PYTHONHOME = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' PYTHONPATH = '.:/home/procstoo/api.proconnect-edu.online/' program name = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' isolated = 0 environment = 1 user site = 1 safe_path = 0 import site = 1 is in build tree = 0 stdlib dir = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11' sys._base_executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.base_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.base_exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.platlibdir = 'lib64' sys.executable = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/bin/python' sys.prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.exec_prefix = '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11' sys.path = [ '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/api.proconnect-edu.online', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python311.zip', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11', '/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x00007f16c0121740 (most recent call first): Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 172, in load_source module = _load(spec) ^^^^^^^^^^^ File "", line 721, in _load File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 614, in _exec File "", line 558, in _init_module_attrs File "", line 398, in cached File "", line 570, in _get_cached File "", line 463, in cache_from_source File "", line 134, in _path_split RecursionError: maximum recursion depth exceeded Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 172, in load_source module = _load(spec) ^^^^^^^^^^^ File "", line 721, in _load File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 614, in _exec File "", line 558, in _init_module_attrs File "", line 398, in cached File "", line 570, in _get_cached File "", line 463, in cache_from_source File "", line 134, in _path_split RecursionError: maximum recursion depth exceeded Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 172, in load_source module = _load(spec) ^^^^^^^^^^^ File "", line 721, in _load File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 614, in _exec File "", line 558, in _init_module_attrs File "", line 398, in cached File "", line 570, in _get_cached File "", line 463, in cache_from_source File "", line 134, in _path_split RecursionError: maximum recursion depth exceeded Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 172, in load_source module = _load(spec) ^^^^^^^^^^^ File "", line 721, in _load File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 621, in _exec File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "passenger_wsgi.py", line 8, in wsgi = imp.load_source('wsgi', 'passenger_wsgi.py') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/imp.py", line 170, in load_source module = _exec(spec, sys.modules[name]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 614, in _exec File "", line 558, in _init_module_attrs File "", line 398, in cached File "", line 570, in _get_cached File "", line 463, in cache_from_source File "", line 134, in _path_split RecursionError: maximum recursion depth exceeded [EMAIL SUCCESS] Email sent successfully to eldadavid-mtcfoundation@chellaramsplc.com (Resend ID: f20eacb0-5fca-4519-9018-bad7eaf1d4fa) /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:366: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 65, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 37, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Unhandled exception: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1310, in _checkout raise exc.InvalidatePoolError() sqlalchemy.exc.InvalidatePoolError: () During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1344, in _checkout with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1341, in _checkout fairy._connection_record.get_connection() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 837, in get_connection self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 291, in app solved_result = await solve_dependencies( ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/dependencies/utils.py", line 640, in solve_dependencies solved = await run_in_threadpool(call, **solved_result.values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/concurrency.py", line 39, in run_in_threadpool return await anyio.to_thread.run_sync(func, *args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/anyio/to_thread.py", line 63, in run_sync return await get_async_backend().run_sync_in_worker_thread( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 2502, in run_sync_in_worker_thread return await future ^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 986, in run result = context.run(func, *args) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 54, in get_current_admin user = db.query(AdminUser).filter(AdminUser.id == user_id).first() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1344, in _checkout with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1341, in _checkout fairy._connection_record.get_connection() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 837, in get_connection self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 717, in checkout with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 715, in checkout dbapi_connection = rec.get_connection() ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 837, in get_connection self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 291, in app solved_result = await solve_dependencies( ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/dependencies/utils.py", line 640, in solve_dependencies solved = await run_in_threadpool(call, **solved_result.values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/concurrency.py", line 39, in run_in_threadpool return await anyio.to_thread.run_sync(func, *args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/anyio/to_thread.py", line 63, in run_sync return await get_async_backend().run_sync_in_worker_thread( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 2502, in run_sync_in_worker_thread return await future ^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 986, in run result = context.run(func, *args) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 54, in get_current_admin user = db.query(AdminUser).filter(AdminUser.id == user_id).first() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 717, in checkout with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 715, in checkout dbapi_connection = rec.get_connection() ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 837, in get_connection self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 717, in checkout with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 715, in checkout dbapi_connection = rec.get_connection() ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 837, in get_connection self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 717, in checkout with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 715, in checkout dbapi_connection = rec.get_connection() ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 837, in get_connection self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 717, in checkout with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 715, in checkout dbapi_connection = rec.get_connection() ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 837, in get_connection self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 717, in checkout with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 715, in checkout dbapi_connection = rec.get_connection() ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 837, in get_connection self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Error in unified_login: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 164, in unified_login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: no pg_hba.conf entry for host "::1", user "procstoo_pouadmin", database "procstoo_pou", SSL off (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py", line 64, in create_waitlist_entry ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/passenger_wsgi.py", line 26, in from app.main import app File "/home/procstoo/api.proconnect-edu.online/app/main.py", line 6, in from app.api.v1 import ( File "/home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py", line 9, in from app.api.deps import get_current_admin, get_current_user, get_db, require_user_type File "/home/procstoo/api.proconnect-edu.online/app/api/deps.py", line 9, in from app.database import get_db File "/home/procstoo/api.proconnect-edu.online/app/database.py", line 13, in engine = create_engine(settings.database_url, pool_pre_ping=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in create_engine File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 546, in create_engine u = _url.make_url(url) ^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 842, in make_url return _parse_url(name_or_url) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/url.py", line 908, in _parse_url raise exc.ArgumentError( sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '' /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Error in unified_login: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 164, in unified_login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.errors.UndefinedTable) relation "admin_users" does not exist LINE 2: FROM admin_users ^ [SQL: SELECT admin_users.id AS admin_users_id, admin_users.username AS admin_users_username, admin_users.email AS admin_users_email, admin_users.password_hash AS admin_users_password_hash, admin_users.role AS admin_users_role, admin_users.is_active AS admin_users_is_active, admin_users.last_login AS admin_users_last_login, admin_users.created_at AS admin_users_created_at, admin_users.updated_at AS admin_users_updated_at FROM admin_users WHERE admin_users.username = %(username_1)s OR admin_users.email = %(email_1)s LIMIT %(param_1)s] [parameters: {'username_1': 'admin', 'email_1': 'admin', 'param_1': 1}] (Background on this error at: https://sqlalche.me/e/20/f405) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 1967, in _exec_single_context self.dialect.do_execute( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 941, in do_execute cursor.execute(statement, parameters) psycopg2.errors.UndefinedTable: relation "admin_users" does not exist LINE 2: FROM admin_users ^ The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2247, in _execute_internal result: Result[Any] = compile_state_cls.orm_execute_statement( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/context.py", line 305, in orm_execute_statement result = conn.execute( ^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 1418, in execute return meth( ^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/sql/elements.py", line 515, in _execute_on_connection return connection._execute_clauseelement( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 1640, in _execute_clauseelement ret = self._execute_context( ^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 1846, in _execute_context return self._exec_single_context( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 1986, in _exec_single_context self._handle_dbapi_exception( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2355, in _handle_dbapi_exception raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 1967, in _exec_single_context self.dialect.do_execute( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 941, in do_execute cursor.execute(statement, parameters) sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedTable) relation "admin_users" does not exist LINE 2: FROM admin_users ^ [SQL: SELECT admin_users.id AS admin_users_id, admin_users.username AS admin_users_username, admin_users.email AS admin_users_email, admin_users.password_hash AS admin_users_password_hash, admin_users.role AS admin_users_role, admin_users.is_active AS admin_users_is_active, admin_users.last_login AS admin_users_last_login, admin_users.created_at AS admin_users_created_at, admin_users.updated_at AS admin_users_updated_at FROM admin_users WHERE admin_users.username = %(username_1)s OR admin_users.email = %(email_1)s LIMIT %(param_1)s] [parameters: {'username_1': 'admin', 'email_1': 'admin', 'param_1': 1}] (Background on this error at: https://sqlalche.me/e/20/f405) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:62: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py", line 65, in create_waitlist_entry ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py", line 65, in create_waitlist_entry ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py", line 65, in create_waitlist_entry ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py", line 65, in create_waitlist_entry ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py", line 65, in create_waitlist_entry ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py", line 65, in create_waitlist_entry ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( Unhandled exception: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.OperationalError: connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py", line 36, in login ).first() ^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2728, in first return self.limit(1)._iter().first() # type: ignore ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2827, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( ^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2362, in execute return self._execute_internal( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2237, in _execute_internal conn = self._connection_for_bind(bind) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 2106, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 2, in _connection_for_bind File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) ^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/orm/session.py", line 1189, in _connection_for_bind conn = bind.connect() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3278, in connect return self._connection_cls(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 148, in __init__ Connection._handle_dbapi_exception_noconnection( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 2442, in _handle_dbapi_exception_noconnection raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 146, in __init__ self._dbapi_connection = engine.raw_connection() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/base.py", line 3302, in raw_connection return self.pool.connect() ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 449, in connect return _ConnectionFairy._checkout(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 1263, in _checkout fairy = _ConnectionRecord.checkout(pool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 712, in checkout rec = pool._do_get() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 179, in _do_get with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/impl.py", line 177, in _do_get return self._create_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 390, in _create_connection return _ConnectionRecord(self) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 674, in __init__ self.__connect() File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 900, in __connect with util.safe_reraise(): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/pool/base.py", line 896, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/create.py", line 643, in connect return dialect.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/sqlalchemy/engine/default.py", line 621, in connect return self.loaded_dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "server.tabsoltech.com" (203.161.50.96), port 5433 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? (Background on this error at: https://sqlalche.me/e/20/e3q8) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 65, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 37, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 58, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 58, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:96: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.official_email).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:96: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.official_email).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/application_service.py:44: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_app = db.query(Application).filter( /home/procstoo/api.proconnect-edu.online/app/services/application_service.py:44: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_app = db.query(Application).filter( Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:153: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) entry = db.query(Waitlist).filter(Waitlist.id == ref_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/application_service.py:44: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_app = db.query(Application).filter( /home/procstoo/api.proconnect-edu.online/app/services/application_service.py:44: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_app = db.query(Application).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Unhandled exception: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions Traceback (most recent call last): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in __call__ await self.simple_response(scope, receive, send, request_headers=headers) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/cors.py", line 144, in simple_response await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__ await self.middleware_stack(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 735, in app await route.handle(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle await self.app(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 76, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app raise exc File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app await app(scope, receive, sender) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/starlette/routing.py", line 73, in app response = await f(request) ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/api/v1/applications.py", line 327, in send_admission_letter pdf_bytes = PDFService.generate_admission_letter(application) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/pdf_service.py", line 67, in generate_admission_letter pdf_bytes = _HTML(string=html_content).write_pdf() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 265, in write_pdf self.render(font_config, counter_style, **options) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/__init__.py", line 222, in render return Document._render(self, font_config, counter_style, options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in _render [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/document.py", line 266, in [Page(page_box) for page_box in page_boxes], ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/__init__.py", line 130, in layout_document pages = list(make_all_pages(context, root_box, html, pages)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 913, in make_all_pages page, resume_at = remake_page(i, group_i, context, root_box, html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 850, in remake_page page, resume_at, next_page = make_page( ^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/page.py", line 649, in make_page root_box, resume_at, next_page, _, _, _ = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 720, in block_container_layout next_page, new_children, new_max_lines) = _in_flow_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 512, in _in_flow_layout collapsing_through, max_lines) = block_level_layout( ^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 59, in block_level_layout return block_level_layout_switch( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 75, in block_level_layout_switch return block_box_layout( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 124, in block_box_layout result = block_container_layout( ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 709, in block_container_layout new_footnotes, max_lines) = _linebox_layout( ^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/block.py", line 349, in _linebox_layout for i, (line, resume_at) in enumerate(lines_iterator): File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 38, in iter_line_boxes line, resume_at = get_next_linebox( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 95, in get_next_linebox last_letter, float_width) = split_inline_box( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 720, in split_inline_box split_inline_level( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 471, in split_inline_level new_box, skip, preserved_line_break = split_text_box( ^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/layout/inline.py", line 891, in split_text_box layout, length, resume_index, width, height, baseline = split_first_line( ^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 285, in split_first_line layout = create_layout( ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 236, in create_layout layout = Layout(context, style, justification_spacing, max_width) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 62, in __init__ self.setup(context, style) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/weasyprint/text/line_break.py", line 78, in setup pango.pango_context_set_round_glyph_positions(pango_context, False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 914, in __getattr__ make_accessor(name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 910, in make_accessor accessors[name](name) File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib64/python3.11/site-packages/cffi/api.py", line 840, in accessor_function value = backendlib.load_function(BType, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() WeasyPrint runtime error, falling back to xhtml2pdf: function/symbol 'pango_context_set_round_glyph_positions' not found in library 'libpango-1.0.so.0': /lib64/libpango-1.0.so.0: undefined symbol: pango_context_set_round_glyph_positions /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1766: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1766: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/academics.py:35: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) query = db.query(Programme) /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1766: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1766: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:187: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.email).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:187: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.email).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( Failed to send email to ['dorcasj760@gmail.com']: Failed to parse Resend API response. Please try again. Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/email_service.py", line 61, in send_email email = resend.Emails.send(params) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/emails/_emails.py", line 168, in send ).perform_with_content() ^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/request.py", line 74, in perform_with_content resp = self.perform() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/request.py", line 47, in perform raise_for_code_and_type( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/exceptions.py", line 219, in raise_for_code_and_type raise ResendError( resend.exceptions.ResendError: Failed to parse Resend API response. Please try again. Failed to send waitlist confirmation email to dorcasj760@gmail.com: Failed to parse Resend API response. Please try again. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:63: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:68: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:68: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.official_email).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.official_email).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1842: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1842: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1842: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1842: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1842: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1842: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() [UID:855][1720228] Child process with pid: 1720654 was killed by signal: 15, core dumped: no [UID:855][1720228] Child process with pid: 1720466 was killed by signal: 15, core dumped: no [UID:855][1720228] Child process with pid: 1739863 was killed by signal: 15, core dumped: no /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( Failed to send email to ['demibyte@yahoo.co.uk']: You have reached your monthly email sending quota. Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/email_service.py", line 61, in send_email email = resend.Emails.send(params) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/emails/_emails.py", line 168, in send ).perform_with_content() ^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/request.py", line 74, in perform_with_content resp = self.perform() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/request.py", line 57, in perform raise_for_code_and_type( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/exceptions.py", line 205, in raise_for_code_and_type raise ResendError( resend.exceptions.ResendError: You have reached your monthly email sending quota. Failed to send waitlist confirmation email to demibyte@yahoo.co.uk: You have reached your monthly email sending quota. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( Failed to send email to ['oluwaseyifunmi234@gmail.com']: You have reached your monthly email sending quota. Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/email_service.py", line 61, in send_email email = resend.Emails.send(params) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/emails/_emails.py", line 168, in send ).perform_with_content() ^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/request.py", line 74, in perform_with_content resp = self.perform() ^^^^^^^^^^^^^^ File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/request.py", line 57, in perform raise_for_code_and_type( File "/home/procstoo/virtualenv/api.proconnect-edu.online/3.11/lib/python3.11/site-packages/resend/exceptions.py", line 205, in raise_for_code_and_type raise ResendError( resend.exceptions.ResendError: You have reached your monthly email sending quota. Failed to send waitlist confirmation email to oluwaseyifunmi234@gmail.com: You have reached your monthly email sending quota. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:213: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.email).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:213: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.email).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:213: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.email).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:213: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_user = db.query(User).filter(User.email == payload.email).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1957: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) ep = db.query(EducationalPartner).filter(EducationalPartner.id == body.partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1957: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) ep = db.query(EducationalPartner).filter(EducationalPartner.id == body.partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1244: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1244: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1244: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1244: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:76: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails. /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/partners.py:1884: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) partner = db.query(EducationalPartner).filter(EducationalPartner.id == partner_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:135: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(User).filter(User.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:130: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:162: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) admin_user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/waitlist.py:98: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing = db.query(Waitlist).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/v1/auth.py:34: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter( /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/api/deps.py:54: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) user = db.query(AdminUser).filter(AdminUser.id == user_id).first() /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:386: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(BizVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.corporate_partner' will copy column corporate_partners.id to column discovery_sessions.corporate_partner_id, which conflicts with relationship(s): 'CorporatePartner.discovery_sessions' (copies corporate_partners.id to discovery_sessions.corporate_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.corporate_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( /home/procstoo/api.proconnect-edu.online/app/services/verification_service.py:33: SAWarning: relationship 'DiscoverySession.educational_partner' will copy column educational_partners.id to column discovery_sessions.educational_partner_id, which conflicts with relationship(s): 'EducationalPartner.discovery_sessions' (copies educational_partners.id to discovery_sessions.educational_partner_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="discovery_sessions"' to the 'DiscoverySession.educational_partner' relationship. (Background on this warning at: https://sqlalche.me/e/20/qzyx) (This warning originated from the `configure_mappers()` process, which was invoked automatically in response to a user-initiated operation.) existing_verification = db.query(NINVerification).filter( Failed to create Google Calendar/Meet event: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 76, in create_discovery_event service = GoogleCalendarService._get_calendar_client() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/procstoo/api.proconnect-edu.online/app/services/google_calendar_service.py", line 41, in _get_calendar_client info = json.loads(settings.google_service_account_json) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/alt/python311/lib64/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Discovery session booked but no calendar link; skipping emails.