Running behind an ssl proxy
Hi, I would like to deploy the Docker image from https://hub.docker.com/r/dpage/pgadmin4/ and access it when it is deployed behind an SSL proxy server (in our case it is Traefik). It would be ideal if PgAdmin could be configured to run behind the SSL proxy server and have the proxy server terminate the SSL connection. In this case, the URLs generated by PgAdmin should be https:// prefixed even though PgAdmin itself is only listening on the HTTP port. Could anyone recommend how this could be achieved in PgAdmin or what it needs to behave this way? Regards, Aron
Building releases...
... is really not going well today.
After arguing with PIP on Mac for some time, I eventually managed to get a
build out. That required a manual update of my system to 9.0.3 to ensure
TLS 1.2 worked, and then changing to build such that we only force our own
build of Psycopg2, and not other Python packages. I *think* these issues
are related to the whole PyPi TLS 1.2/PIP 9.0.3 brownouts and other works
they've been doing.
The Windows build is a whole other ballgame. The build itself runs just
fine, but we end up with the following error in the log:
Traceback (most recent call last):
File "C:/Program Files/pgAdmin 4/v3/web/pgAdmin4.py", line 70, in
app = create_app()
File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\__init__.py", line 367,
in create_app
driver.init_app(app)
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\__init__.py", line 40, in init_app
DriverRegistry.load_drivers()
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\registry.py", line 88, in load_drivers
module = import_module(module_name)
File "C:/Program Files/pgAdmin 4/v3/venv\lib\importlib\__init__.py", line
37, in import_module
__import__(name)
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\psycopg2\__init__.py", line 26, in
from .connection import Connection
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\psycopg2\connection.py", line 25, in
from pgadmin.utils.crypto import decrypt
File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\crypto.py", line
16, in
from Crypto.Cipher import AES
File "C:/Program Files/pgAdmin
4/v3/venv/Lib/site-packages\Crypto\Cipher\__init__.py", line 3, in
from Crypto.Cipher._mode_ecb import _create_ecb_cipher
File "C:/Program Files/pgAdmin
4/v3/venv/Lib/site-packages\Crypto\Cipher\_mode_ecb.py", line 46, in
"""
File "C:/Program Files/pgAdmin
4/v3/venv/Lib/site-packages\Crypto\Util\_raw_api.py", line 258, in
load_pycryptodome_raw_lib
raise OSError("Cannot load native module '%s': %s" % (name, ",
".join(attempts)))
OSError: Cannot load native module 'Crypto.Cipher._raw_ecb': Trying
'_raw_ecb.pyd': [Error 126] The specified module could not be found
Exception KeyError: KeyError(3644,) in ignored
The module does exist of course in the Crypto\Cipher directory.
Murtuza, Khushboo; have you got it running on pgAdmin recently?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Re: Building releases...
Did not try running pgAdmin4 on windows from git repo.
Let me get the latest pull and check.
--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Mon, Apr 9, 2018 at 5:53 PM, Dave Page wrote:
> ... is really not going well today.
>
> After arguing with PIP on Mac for some time, I eventually managed to get a
> build out. That required a manual update of my system to 9.0.3 to ensure
> TLS 1.2 worked, and then changing to build such that we only force our own
> build of Psycopg2, and not other Python packages. I *think* these issues
> are related to the whole PyPi TLS 1.2/PIP 9.0.3 brownouts and other works
> they've been doing.
>
> The Windows build is a whole other ballgame. The build itself runs just
> fine, but we end up with the following error in the log:
>
> Traceback (most recent call last):
> File "C:/Program Files/pgAdmin 4/v3/web/pgAdmin4.py", line 70, in
>
> app = create_app()
> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\__init__.py", line 367,
> in create_app
> driver.init_app(app)
> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\driver\__init__.py",
> line 40, in init_app
> DriverRegistry.load_drivers()
> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\driver\registry.py",
> line 88, in load_drivers
> module = import_module(module_name)
> File "C:/Program Files/pgAdmin 4/v3/venv\lib\importlib\__init__.py",
> line 37, in import_module
> __import__(name)
> File "C:\Program Files\pgAdmin
> 4\v3\web\pgadmin\utils\driver\psycopg2\__init__.py",
> line 26, in
> from .connection import Connection
> File "C:\Program Files\pgAdmin
> 4\v3\web\pgadmin\utils\driver\psycopg2\connection.py",
> line 25, in
> from pgadmin.utils.crypto import decrypt
> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\crypto.py", line
> 16, in
> from Crypto.Cipher import AES
> File "C:/Program Files/pgAdmin
> 4/v3/venv/Lib/site-packages\Crypto\Cipher\__init__.py",
> line 3, in
> from Crypto.Cipher._mode_ecb import _create_ecb_cipher
> File "C:/Program Files/pgAdmin
> 4/v3/venv/Lib/site-packages\Crypto\Cipher\_mode_ecb.py",
> line 46, in
> """
> File "C:/Program Files/pgAdmin
> 4/v3/venv/Lib/site-packages\Crypto\Util\_raw_api.py",
> line 258, in load_pycryptodome_raw_lib
> raise OSError("Cannot load native module '%s': %s" % (name, ",
> ".join(attempts)))
> OSError: Cannot load native module 'Crypto.Cipher._raw_ecb': Trying
> '_raw_ecb.pyd': [Error 126] The specified module could not be found
> Exception KeyError: KeyError(3644,) in 'C:/Program Files/pgAdmin 4/v3/venv\lib\threading.py'> ignored
>
> The module does exist of course in the Crypto\Cipher directory.
>
> Murtuza, Khushboo; have you got it running on pgAdmin recently?
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
Re: Building releases...
Oh yeah - I forgot to mention that running it in PyCharms seems to work.
The issue comes when using the runtime from what I can see (even using the
exact same venv that works otherwise).
On Mon, Apr 9, 2018 at 1:46 PM, Murtuza Zabuawala <
murtuza.zabuaw...@enterprisedb.com> wrote:
> Did not try running pgAdmin4 on windows from git repo.
> Let me get the latest pull and check.
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
> On Mon, Apr 9, 2018 at 5:53 PM, Dave Page wrote:
>
>> ... is really not going well today.
>>
>> After arguing with PIP on Mac for some time, I eventually managed to get
>> a build out. That required a manual update of my system to 9.0.3 to ensure
>> TLS 1.2 worked, and then changing to build such that we only force our own
>> build of Psycopg2, and not other Python packages. I *think* these issues
>> are related to the whole PyPi TLS 1.2/PIP 9.0.3 brownouts and other works
>> they've been doing.
>>
>> The Windows build is a whole other ballgame. The build itself runs just
>> fine, but we end up with the following error in the log:
>>
>> Traceback (most recent call last):
>> File "C:/Program Files/pgAdmin 4/v3/web/pgAdmin4.py", line 70, in
>>
>> app = create_app()
>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\__init__.py", line 367,
>> in create_app
>> driver.init_app(app)
>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\driver\__init__.py",
>> line 40, in init_app
>> DriverRegistry.load_drivers()
>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\driver\registry.py",
>> line 88, in load_drivers
>> module = import_module(module_name)
>> File "C:/Program Files/pgAdmin 4/v3/venv\lib\importlib\__init__.py",
>> line 37, in import_module
>> __import__(name)
>> File "C:\Program Files\pgAdmin
>> 4\v3\web\pgadmin\utils\driver\psycopg2\__init__.py",
>> line 26, in
>> from .connection import Connection
>> File "C:\Program Files\pgAdmin
>> 4\v3\web\pgadmin\utils\driver\psycopg2\connection.py",
>> line 25, in
>> from pgadmin.utils.crypto import decrypt
>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\crypto.py", line
>> 16, in
>> from Crypto.Cipher import AES
>> File "C:/Program Files/pgAdmin
>> 4/v3/venv/Lib/site-packages\Crypto\Cipher\__init__.py",
>> line 3, in
>> from Crypto.Cipher._mode_ecb import _create_ecb_cipher
>> File "C:/Program Files/pgAdmin
>> 4/v3/venv/Lib/site-packages\Crypto\Cipher\_mode_ecb.py",
>> line 46, in
>> """
>> File "C:/Program Files/pgAdmin
>> 4/v3/venv/Lib/site-packages\Crypto\Util\_raw_api.py",
>> line 258, in load_pycryptodome_raw_lib
>> raise OSError("Cannot load native module '%s': %s" % (name, ",
>> ".join(attempts)))
>> OSError: Cannot load native module 'Crypto.Cipher._raw_ecb': Trying
>> '_raw_ecb.pyd': [Error 126] The specified module could not be found
>> Exception KeyError: KeyError(3644,) in > 'C:/Program Files/pgAdmin 4/v3/venv\lib\threading.py'> ignored
>>
>> The module does exist of course in the Crypto\Cipher directory.
>>
>> Murtuza, Khushboo; have you got it running on pgAdmin recently?
>>
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Re: Building releases...
On Mon, Apr 9, 2018 at 6:19 PM, Dave Page wrote:
> Oh yeah - I forgot to mention that running it in PyCharms seems to work.
> The issue comes when using the runtime from what I can see (even using the
> exact same venv that works otherwise).
>
> Didn't try on windows. Let me try.
> On Mon, Apr 9, 2018 at 1:46 PM, Murtuza Zabuawala enterprisedb.com> wrote:
>
>> Did not try running pgAdmin4 on windows from git repo.
>> Let me get the latest pull and check.
>>
>> --
>> Regards,
>> Murtuza Zabuawala
>> EnterpriseDB: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>>
>> On Mon, Apr 9, 2018 at 5:53 PM, Dave Page wrote:
>>
>>> ... is really not going well today.
>>>
>>> After arguing with PIP on Mac for some time, I eventually managed to get
>>> a build out. That required a manual update of my system to 9.0.3 to ensure
>>> TLS 1.2 worked, and then changing to build such that we only force our own
>>> build of Psycopg2, and not other Python packages. I *think* these issues
>>> are related to the whole PyPi TLS 1.2/PIP 9.0.3 brownouts and other works
>>> they've been doing.
>>>
>>> The Windows build is a whole other ballgame. The build itself runs just
>>> fine, but we end up with the following error in the log:
>>>
>>> Traceback (most recent call last):
>>> File "C:/Program Files/pgAdmin 4/v3/web/pgAdmin4.py", line 70, in
>>>
>>> app = create_app()
>>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\__init__.py", line
>>> 367, in create_app
>>> driver.init_app(app)
>>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\driver\__init__.py",
>>> line 40, in init_app
>>> DriverRegistry.load_drivers()
>>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\driver\registry.py",
>>> line 88, in load_drivers
>>> module = import_module(module_name)
>>> File "C:/Program Files/pgAdmin 4/v3/venv\lib\importlib\__init__.py",
>>> line 37, in import_module
>>> __import__(name)
>>> File "C:\Program Files\pgAdmin
>>> 4\v3\web\pgadmin\utils\driver\psycopg2\__init__.py",
>>> line 26, in
>>> from .connection import Connection
>>> File "C:\Program Files\pgAdmin
>>> 4\v3\web\pgadmin\utils\driver\psycopg2\connection.py",
>>> line 25, in
>>> from pgadmin.utils.crypto import decrypt
>>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\crypto.py",
>>> line 16, in
>>> from Crypto.Cipher import AES
>>> File "C:/Program Files/pgAdmin
>>> 4/v3/venv/Lib/site-packages\Crypto\Cipher\__init__.py",
>>> line 3, in
>>> from Crypto.Cipher._mode_ecb import _create_ecb_cipher
>>> File "C:/Program Files/pgAdmin
>>> 4/v3/venv/Lib/site-packages\Crypto\Cipher\_mode_ecb.py",
>>> line 46, in
>>> """
>>> File "C:/Program Files/pgAdmin
>>> 4/v3/venv/Lib/site-packages\Crypto\Util\_raw_api.py",
>>> line 258, in load_pycryptodome_raw_lib
>>> raise OSError("Cannot load native module '%s': %s" % (name, ",
>>> ".join(attempts)))
>>> OSError: Cannot load native module 'Crypto.Cipher._raw_ecb': Trying
>>> '_raw_ecb.pyd': [Error 126] The specified module could not be found
>>> Exception KeyError: KeyError(3644,) in >> 'C:/Program Files/pgAdmin 4/v3/venv\lib\threading.py'> ignored
>>>
>>> The module does exist of course in the Crypto\Cipher directory.
>>>
>>> Murtuza, Khushboo; have you got it running on pgAdmin recently?
>>>
>>>
>>> --
>>> Dave Page
>>> Blog: http://pgsnake.blogspot.com
>>> Twitter: @pgsnake
>>>
>>> EnterpriseDB UK: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>>
>>
>>
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
Re: Building releases...
Hi Dave,
On Mon, Apr 9, 2018 at 6:33 PM, Khushboo Vashi <
khushboo.va...@enterprisedb.com> wrote:
>
>
> On Mon, Apr 9, 2018 at 6:19 PM, Dave Page wrote:
>
>> Oh yeah - I forgot to mention that running it in PyCharms seems to work.
>> The issue comes when using the runtime from what I can see (even using the
>> exact same venv that works otherwise).
>>
>> Didn't try on windows. Let me try.
>
>> On Mon, Apr 9, 2018 at 1:46 PM, Murtuza Zabuawala <
>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>
>>> Did not try running pgAdmin4 on windows from git repo.
>>> Let me get the latest pull and check.
>>>
>>> --
>>> Regards,
>>> Murtuza Zabuawala
>>> EnterpriseDB: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>>
>>>
>>> On Mon, Apr 9, 2018 at 5:53 PM, Dave Page wrote:
>>>
... is really not going well today.
After arguing with PIP on Mac for some time, I eventually managed to
get a build out. That required a manual update of my system to 9.0.3 to
ensure TLS 1.2 worked, and then changing to build such that we only force
our own build of Psycopg2, and not other Python packages. I *think* these
issues are related to the whole PyPi TLS 1.2/PIP 9.0.3 brownouts and other
works they've been doing.
The Windows build is a whole other ballgame. The build itself runs just
fine, but we end up with the following error in the log:
Traceback (most recent call last):
File "C:/Program Files/pgAdmin 4/v3/web/pgAdmin4.py", line 70, in
app = create_app()
File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\__init__.py", line
367, in create_app
driver.init_app(app)
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\__init__.py",
line 40, in init_app
DriverRegistry.load_drivers()
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\registry.py",
line 88, in load_drivers
module = import_module(module_name)
File "C:/Program Files/pgAdmin 4/v3/venv\lib\importlib\__init__.py",
line 37, in import_module
__import__(name)
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\psycopg2\__init__.py",
line 26, in
from .connection import Connection
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\psycopg2\connection.py",
line 25, in
from pgadmin.utils.crypto import decrypt
File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\crypto.py",
line 16, in
from Crypto.Cipher import AES
File "C:/Program Files/pgAdmin
4/v3/venv/Lib/site-packages\Crypto\Cipher\__init__.py",
line 3, in
from Crypto.Cipher._mode_ecb import _create_ecb_cipher
File "C:/Program Files/pgAdmin
4/v3/venv/Lib/site-packages\Crypto\Cipher\_mode_ecb.py",
line 46, in
"""
File "C:/Program Files/pgAdmin
4/v3/venv/Lib/site-packages\Crypto\Util\_raw_api.py",
line 258, in load_pycryptodome_raw_lib
raise OSError("Cannot load native module '%s': %s" % (name, ",
".join(attempts)))
OSError: Cannot load native module 'Crypto.Cipher._raw_ecb': Trying
'_raw_ecb.pyd': [Error 126] The specified module could not be found
Exception KeyError: KeyError(3644,) in >>> 'C:/Program Files/pgAdmin 4/v3/venv\lib\threading.py'> ignored
The module does exist of course in the Crypto\Cipher directory.
>>>
Everything works fine on my windows machine with Python 3.5.
Any specific scenarios ?
>
Murtuza, Khushboo; have you got it running on pgAdmin recently?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
>>>
>>>
>>
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
>
Re: Building releases...
On Mon, Apr 9, 2018 at 2:20 PM, Neel Patel
wrote:
> Hi Dave,
>
> On Mon, Apr 9, 2018 at 6:33 PM, Khushboo Vashi <
> khushboo.va...@enterprisedb.com> wrote:
>
>>
>>
>> On Mon, Apr 9, 2018 at 6:19 PM, Dave Page wrote:
>>
>>> Oh yeah - I forgot to mention that running it in PyCharms seems to work.
>>> The issue comes when using the runtime from what I can see (even using the
>>> exact same venv that works otherwise).
>>>
>>> Didn't try on windows. Let me try.
>>
>>> On Mon, Apr 9, 2018 at 1:46 PM, Murtuza Zabuawala <
>>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>>
Did not try running pgAdmin4 on windows from git repo.
Let me get the latest pull and check.
--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Mon, Apr 9, 2018 at 5:53 PM, Dave Page wrote:
> ... is really not going well today.
>
> After arguing with PIP on Mac for some time, I eventually managed to
> get a build out. That required a manual update of my system to 9.0.3 to
> ensure TLS 1.2 worked, and then changing to build such that we only force
> our own build of Psycopg2, and not other Python packages. I *think* these
> issues are related to the whole PyPi TLS 1.2/PIP 9.0.3 brownouts and other
> works they've been doing.
>
> The Windows build is a whole other ballgame. The build itself runs
> just fine, but we end up with the following error in the log:
>
> Traceback (most recent call last):
> File "C:/Program Files/pgAdmin 4/v3/web/pgAdmin4.py", line 70, in
>
> app = create_app()
> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\__init__.py", line
> 367, in create_app
> driver.init_app(app)
> File "C:\Program Files\pgAdmin
> 4\v3\web\pgadmin\utils\driver\__init__.py",
> line 40, in init_app
> DriverRegistry.load_drivers()
> File "C:\Program Files\pgAdmin
> 4\v3\web\pgadmin\utils\driver\registry.py",
> line 88, in load_drivers
> module = import_module(module_name)
> File "C:/Program Files/pgAdmin 4/v3/venv\lib\importlib\__init__.py",
> line 37, in import_module
> __import__(name)
> File "C:\Program Files\pgAdmin
> 4\v3\web\pgadmin\utils\driver\psycopg2\__init__.py",
> line 26, in
> from .connection import Connection
> File "C:\Program Files\pgAdmin
> 4\v3\web\pgadmin\utils\driver\psycopg2\connection.py",
> line 25, in
> from pgadmin.utils.crypto import decrypt
> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\crypto.py",
> line 16, in
> from Crypto.Cipher import AES
> File "C:/Program Files/pgAdmin
> 4/v3/venv/Lib/site-packages\Crypto\Cipher\__init__.py",
> line 3, in
> from Crypto.Cipher._mode_ecb import _create_ecb_cipher
> File "C:/Program Files/pgAdmin
> 4/v3/venv/Lib/site-packages\Crypto\Cipher\_mode_ecb.py",
> line 46, in
> """
> File "C:/Program Files/pgAdmin
> 4/v3/venv/Lib/site-packages\Crypto\Util\_raw_api.py",
> line 258, in load_pycryptodome_raw_lib
> raise OSError("Cannot load native module '%s': %s" % (name, ",
> ".join(attempts)))
> OSError: Cannot load native module 'Crypto.Cipher._raw_ecb': Trying
> '_raw_ecb.pyd': [Error 126] The specified module could not be found
> Exception KeyError: KeyError(3644,) in 'C:/Program Files/pgAdmin 4/v3/venv\lib\threading.py'> ignored
>
> The module does exist of course in the Crypto\Cipher directory.
>
> Everything works fine on my windows machine with Python 3.5.
> Any specific scenarios ?
>
Standard release build using Python 2.7;
make x86
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Re: Building releases...
On Mon, Apr 9, 2018 at 6:51 PM, Dave Page wrote:
>
>
> On Mon, Apr 9, 2018 at 2:20 PM, Neel Patel
> wrote:
>
>> Hi Dave,
>>
>> On Mon, Apr 9, 2018 at 6:33 PM, Khushboo Vashi <
>> khushboo.va...@enterprisedb.com> wrote:
>>
>>>
>>>
>>> On Mon, Apr 9, 2018 at 6:19 PM, Dave Page wrote:
>>>
Oh yeah - I forgot to mention that running it in PyCharms seems to
work. The issue comes when using the runtime from what I can see (even
using the exact same venv that works otherwise).
Didn't try on windows. Let me try.
>>>
On Mon, Apr 9, 2018 at 1:46 PM, Murtuza Zabuawala <
murtuza.zabuaw...@enterprisedb.com> wrote:
> Did not try running pgAdmin4 on windows from git repo.
> Let me get the latest pull and check.
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
> On Mon, Apr 9, 2018 at 5:53 PM, Dave Page wrote:
>
>> ... is really not going well today.
>>
>> After arguing with PIP on Mac for some time, I eventually managed to
>> get a build out. That required a manual update of my system to 9.0.3 to
>> ensure TLS 1.2 worked, and then changing to build such that we only force
>> our own build of Psycopg2, and not other Python packages. I *think* these
>> issues are related to the whole PyPi TLS 1.2/PIP 9.0.3 brownouts and
>> other
>> works they've been doing.
>>
>> The Windows build is a whole other ballgame. The build itself runs
>> just fine, but we end up with the following error in the log:
>>
>> Traceback (most recent call last):
>> File "C:/Program Files/pgAdmin 4/v3/web/pgAdmin4.py", line 70, in
>>
>> app = create_app()
>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\__init__.py", line
>> 367, in create_app
>> driver.init_app(app)
>> File "C:\Program Files\pgAdmin
>> 4\v3\web\pgadmin\utils\driver\__init__.py",
>> line 40, in init_app
>> DriverRegistry.load_drivers()
>> File "C:\Program Files\pgAdmin
>> 4\v3\web\pgadmin\utils\driver\registry.py",
>> line 88, in load_drivers
>> module = import_module(module_name)
>> File "C:/Program Files/pgAdmin 4/v3/venv\lib\importlib\__init__.py",
>> line 37, in import_module
>> __import__(name)
>> File "C:\Program Files\pgAdmin
>> 4\v3\web\pgadmin\utils\driver\psycopg2\__init__.py",
>> line 26, in
>> from .connection import Connection
>> File "C:\Program Files\pgAdmin
>> 4\v3\web\pgadmin\utils\driver\psycopg2\connection.py",
>> line 25, in
>> from pgadmin.utils.crypto import decrypt
>> File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\crypto.py",
>> line 16, in
>> from Crypto.Cipher import AES
>> File "C:/Program Files/pgAdmin
>> 4/v3/venv/Lib/site-packages\Crypto\Cipher\__init__.py",
>> line 3, in
>> from Crypto.Cipher._mode_ecb import _create_ecb_cipher
>> File "C:/Program Files/pgAdmin
>> 4/v3/venv/Lib/site-packages\Crypto\Cipher\_mode_ecb.py",
>> line 46, in
>> """
>> File "C:/Program Files/pgAdmin
>> 4/v3/venv/Lib/site-packages\Crypto\Util\_raw_api.py",
>> line 258, in load_pycryptodome_raw_lib
>> raise OSError("Cannot load native module '%s': %s" % (name, ",
>> ".join(attempts)))
>> OSError: Cannot load native module 'Crypto.Cipher._raw_ecb': Trying
>> '_raw_ecb.pyd': [Error 126] The specified module could not be found
>> Exception KeyError: KeyError(3644,) in > 'C:/Program Files/pgAdmin 4/v3/venv\lib\threading.py'> ignored
>>
>> The module does exist of course in the Crypto\Cipher directory.
>>
>
>> Everything works fine on my windows machine with Python 3.5.
>> Any specific scenarios ?
>>
>
> Standard release build using Python 2.7;
>
> make x86
>
Let me try with Python 2.7 x86.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
Re: Building releases...
It works like that for me too. Try running from the runtime.
On Mon, Apr 9, 2018 at 2:39 PM, Murtuza Zabuawala <
murtuza.zabuaw...@enterprisedb.com> wrote:
> I tried and it is working fine.
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
> On Mon, Apr 9, 2018 at 6:57 PM, Neel Patel
> wrote:
>
>>
>>
>> On Mon, Apr 9, 2018 at 6:51 PM, Dave Page wrote:
>>
>>>
>>>
>>> On Mon, Apr 9, 2018 at 2:20 PM, Neel Patel
>>> wrote:
>>>
Hi Dave,
On Mon, Apr 9, 2018 at 6:33 PM, Khushboo Vashi <
khushboo.va...@enterprisedb.com> wrote:
>
>
> On Mon, Apr 9, 2018 at 6:19 PM, Dave Page wrote:
>
>> Oh yeah - I forgot to mention that running it in PyCharms seems to
>> work. The issue comes when using the runtime from what I can see (even
>> using the exact same venv that works otherwise).
>>
>> Didn't try on windows. Let me try.
>
>> On Mon, Apr 9, 2018 at 1:46 PM, Murtuza Zabuawala <
>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>
>>> Did not try running pgAdmin4 on windows from git repo.
>>> Let me get the latest pull and check.
>>>
>>> --
>>> Regards,
>>> Murtuza Zabuawala
>>> EnterpriseDB: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>>
>>>
>>> On Mon, Apr 9, 2018 at 5:53 PM, Dave Page wrote:
>>>
... is really not going well today.
After arguing with PIP on Mac for some time, I eventually managed
to get a build out. That required a manual update of my system to
9.0.3 to
ensure TLS 1.2 worked, and then changing to build such that we only
force
our own build of Psycopg2, and not other Python packages. I *think*
these
issues are related to the whole PyPi TLS 1.2/PIP 9.0.3 brownouts and
other
works they've been doing.
The Windows build is a whole other ballgame. The build itself runs
just fine, but we end up with the following error in the log:
Traceback (most recent call last):
File "C:/Program Files/pgAdmin 4/v3/web/pgAdmin4.py", line 70, in
app = create_app()
File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\__init__.py",
line 367, in create_app
driver.init_app(app)
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\__init__.py",
line 40, in init_app
DriverRegistry.load_drivers()
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\registry.py",
line 88, in load_drivers
module = import_module(module_name)
File "C:/Program Files/pgAdmin 4/v3/venv\lib\importlib\__init__.py",
line 37, in import_module
__import__(name)
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\psycopg2\__init__.py",
line 26, in
from .connection import Connection
File "C:\Program Files\pgAdmin
4\v3\web\pgadmin\utils\driver\psycopg2\connection.py",
line 25, in
from pgadmin.utils.crypto import decrypt
File "C:\Program Files\pgAdmin 4\v3\web\pgadmin\utils\crypto.py",
line 16, in
from Crypto.Cipher import AES
File "C:/Program Files/pgAdmin
4/v3/venv/Lib/site-packages\Crypto\Cipher\__init__.py",
line 3, in
from Crypto.Cipher._mode_ecb import _create_ecb_cipher
File "C:/Program Files/pgAdmin
4/v3/venv/Lib/site-packages\Crypto\Cipher\_mode_ecb.py",
line 46, in
"""
File "C:/Program Files/pgAdmin
4/v3/venv/Lib/site-packages\Crypto\Util\_raw_api.py",
line 258, in load_pycryptodome_raw_lib
raise OSError("Cannot load native module '%s': %s" % (name, ",
".join(attempts)))
OSError: Cannot load native module 'Crypto.Cipher._raw_ecb': Trying
'_raw_ecb.pyd': [Error 126] The specified module could not be found
Exception KeyError: KeyError(3644,) in >>> 'C:/Program Files/pgAdmin 4/v3/venv\lib\threading.py'> ignored
The module does exist of course in the Crypto\Cipher directory.
>>>
Everything works fine on my windows machine with Python 3.5.
Any specific scenarios ?
>>>
>>> Standard release build using Python 2.7;
>>>
>>> make x86
>>>
>> Let me try with Python 2.7 x86.
>>
>>
>>>
>>> --
>>> Dave Page
>>> Blog: http://pgsnake.blogspot.com
>>> Twitter: @pgsnake
>>>
>>> EnterpriseDB UK: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>>
>>
>>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
pgAdmin 4 commit: Ignore generated file
Ignore generated file Branch -- master Details --- https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=9464e04cf851264733cda2e377689ec32901814c Modified Files -- runtime/.gitignore | 1 + 1 file changed, 1 insertion(+)
