Opened 4 years ago

Closed 4 years ago

#18723 closed defect (fixed)

Allow forced proxy

Reported by: vbraun Owned by:
Priority: blocker Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: ncohen Merged in:
Authors: Reviewers: Volker Braun
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description (last modified by vbraun)

Censorship regimes like a restrictive firewall and force use of a http_proxy in order to snoop on their users.

In this case the direct connection to mirrors will fail, and we cannot time the fastest mirror.

Change History (12)

comment:1 Changed 4 years ago by vbraun

  • Branch set to u/vbraun/allow_forced_proxy

comment:2 Changed 4 years ago by vbraun

  • Authors set to Volker Braun
  • Commit set to b0b8360f09b4790f729f759e9f989488593b6707
  • Component changed from PLEASE CHANGE to build
  • Description modified (diff)
  • Status changed from new to needs_review
  • Type changed from PLEASE CHANGE to defect

New commits:

b0b8360Allow for a forced http_proxy behind a firewall

comment:3 Changed 4 years ago by charpent

  • Status changed from needs_review to needs_work

[ Reminder : as you advised, I have edited my .git/config file to use git@... (= forcing SSH) addresses for the upstream locations. ]

Mixed results : added on top of 6.7, I have been able to install fricas. My damn "corporate" proxy gave me cold sweats by hanging for about 3 minutes almost at the end of the download. As I am writing this, the (long) compilation proceeds uneventfully.

But ./sage -optional hangs (no error message for > 5 mn==> Ctrl-C). This happents whether I use an http://... or a git@... address for the "origin" and "trac" upstream address.

I'll wait your feedback before trying to update my 6.7 installation to beta4.

Unless you think that the sage -optional is a separate issue, I think that this needs_work

Last edited 4 years ago by charpent (previous) (diff)

comment:4 follow-up: Changed 4 years ago by vbraun

  • Cc ncohen added
  • Status changed from needs_work to needs_review

IMHO thats a different bug (in Nathan's optional package handling)

comment:5 in reply to: ↑ 4 Changed 4 years ago by ncohen

IMHO thats a different bug (in Nathan's optional package handling)

Is there something wrong in the way the online list of packages is read? It is done with this line:

    f = urllib.urlopen(MIRROR_URL+"/spkg/"+args['category']+"/list")

Nathann

comment:6 follow-up: Changed 4 years ago by vbraun

  • no error handling
  • no logging, so its unclear where the bug is
  • does not work on python 3 (this script might run before we install Sage)

comment:7 in reply to: ↑ 6 Changed 4 years ago by ncohen

  • no error handling
  • no logging, so its unclear where the bug is
  • does not work on python 3 (this script might run before we install Sage)

I expect that exceptions do some error handling already (like timeout?). I did not think that much more was necessary. And I surely did not know that all those scripts had to be python3-compliant O_o

comment:8 Changed 4 years ago by vbraun

This ignores return codes

MIRROR_URL = os.popen("sage-download-file --print-fastest-mirror").read().strip()

A much better api is the newer subprocess.check_output

In any case, none of that belongs to this ticket

comment:9 Changed 4 years ago by vbraun

  • Priority changed from major to blocker

comment:10 Changed 4 years ago by vbraun

  • Branch u/vbraun/allow_forced_proxy deleted
  • Commit b0b8360f09b4790f729f759e9f989488593b6707 deleted
  • Milestone changed from sage-6.8 to sage-duplicate/invalid/wontfix

This is now subsumed in #18748

comment:11 Changed 4 years ago by jdemeyer

  • Authors Volker Braun deleted
  • Reviewers set to Volker Braun
  • Status changed from needs_review to positive_review

comment:12 Changed 4 years ago by vbraun

  • Resolution set to fixed
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.