Opened 7 years ago

Closed 7 years ago

#457 closed defect (fixed)

SasView fails to start if not able to connect to github

Reported by: butler Owned by: mathieu
Priority: major Milestone: SasView 3.1.1
Component: SasView Keywords:
Cc: Work Package: SasView Bug Fixing


Since release 3.0 SasView? now checks for a new version automatically on every startup. Unfortunately in the change from using sasview.latestversion text file in trunk to using a latestversion json file at the checking for a connection got messed up. SasView? is supposed to check an if it has no connection should just say "cannot connect … please try again later".

This needs fixin asap

Change History (3)

comment:1 Changed 7 years ago by butler

  • Owner set to mathieu
  • Status changed from new to assigned

Mathieu has fixed this by moving the reading of the json file into the try block. Testing indicates it now works fine on mac and pc if no internet is available and on pc even if wireless access point is connected but has no internet connection. Need to get confirmation from RAL that it works (as in loads and runs sasview even though it cannot connect to the update server) behind their firewall. Then we can close the ticket.

comment:2 Changed 7 years ago by smk78

Tested ESS Win 7 3.1.0 Build #140 on two machines behind site proxy server:

On PC that had NOT been modified as per FAQ:
SasView? installs and starts after brief delay. If you then force a Check for Updates nothing appears to happen for several seconds, then the window goes 'Not Responding', then it becomes responsive again and 'Could not connect to application server' appears in the status bar.

On PC that HAD been modified as per FAQ:
SasView? installs, starts and Checks for Updates, responding with 'You have the latest version'.

Thus Mathieu's fix would seem to work fine and can be pushed to a point release.

comment:3 Changed 7 years ago by ajj

  • Resolution set to fixed
  • Status changed from assigned to closed

Ricardo has now added changes that allow SasView? to successfully connect from behind a proxy without user modifications, and if that fails still allows SasView? to start e.g. if there is no internet connection.

Note: See TracTickets for help on using tickets.