mdolab / mdolab/pyoptsparse

`import pyoptsparse` hangs (on local machine) when using a vpn

Open
#355 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
270
Forks
123
Avg merge
1d 18h
Merged PRs (30d)
3

Description

Description

This feels like an odd one.
I'm running python on my local machine.
When I'm not connected to a certain VPN, I can import pyoptsparse. When I am connected, it hangs on the import command.
This happens both in a python repl and a jupyter notebook (using the same kernel).

The import command stops hanging and succeeds a few moments after disconnecting the vpn.

This seems very odd to me, as I don't know why there would be any network-calling code in pyoptsparse (other than perhaps to check license for certain optimizers?)

Steps to reproduce issue
  1. Have pyoptsparse installed successfully - I can run Openmdao problems using IPOPT, for example.
  2. Turn on the Pulse Secure VPN so I connect to my lab's servers
  3. Open a new, local python repl or notebook
  4. import pyoptsparse
Current behavior

it hangs until I disconnect from the VPN

Expected behavior

it imports

Code versions
  • Operating System: pop!_os
  • Python: 3.10.2
  • OpenMPI: n/a
  • CGNS: idk what this is
  • PETSc: n/a
  • Compiler: not relevant?
  • This repository: 2.9.2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce import pyoptsparse in a local Python 3.10.2 REPL and Jupyter kernel with the Pulse Secure VPN connected and disconnected. Trace where the import blocks and determine what causes the VPN-dependent delay; done means the import completes while connected, with a regression check for both environments.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.