On Sun, Jan 11, 2015 at 11:43 PM, Andy Bradford
wrote:
> I can set up all kind of QoS on my firewall, but most devices don't
> allow one to request random and routine packet loss and actual
> connection resets (e.g. TCP/IP RST packets) as part of the QoS settings.
> ;-)
Just setu
Andy Bradford wrote:
> I can set up all kind of QoS on my firewall, but most devices don't
> allow one to request random and routine packet loss and actual
> connection resets (e.g. TCP/IP RST packets) as part of the QoS settings.
> ;-)
Just hurl a few gratuitous insults at some bor
Thus said Stephan Beal on Mon, 12 Jan 2015 02:06:30 +0100:
> Seems i can only set "high" and "low" priority, but some boxes may
> allow more details setup.
I can set up all kind of QoS on my firewall, but most devices don't
allow one to request random and routine packet loss and
Thus said Kelly Dean on Sun, 11 Jan 2015 21:37:12 +:
> Just ask your ISP or network administrator to lower your quality of
> service, or try using wifi while a large number of microwave ovens are
> operating nearby.
Wifi with a microwave would have been much easier than what I was doing!
I
On Sun, Jan 11, 2015 at 10:37 PM, Kelly Dean wrote:
> Just ask your ISP or network administrator to lower your quality of service
Actually... some WLAN boxes let you change QoS settings. Mine lets me set
up per-device/per-service rules for traffic priority. Seems i can only set
"high" and "low"
Andy Bradford wrote:
> This explanation seems to fit the facts, but
> reproducing it is a pain.
>
> Let me see if I can cause what I've just stated above to happen.
Just ask your ISP or network administrator to lower your quality of service, or
try using wifi while a large number of microwave ov
Thus said Kelly Dean on Fri, 09 Jan 2015 08:39:35 +:
> HTTPS can't prevent a proxy from dropping packets, including all
> packets after a certain number of bytes for the connection. It also
> doesn't prevent bogus reset packets, though a properly-designed secure
> transport protocol (
Andy Bradford wrote:
> were you presented with a certificate to accept
No.
> is it transparent or does Fossil know it's using a proxy?
It's transparent. Firefox works fine through it (both HTTP and HTTPS), and ssh
works fine through it. Except that it's slow and tends to drop packets and
ra
Thus said Kelly Dean on Thu, 08 Jan 2015 08:52:28 +:
> Yes, a badly-behaving one. That's why I said the network probably
> dropped some packets. But I used HTTPS, so the problems the proxy
> could have introduced would be no more than dropped packets, and bogus
> TCP resets (which SS
Whoever kept trying and failing to download my fossil-src files using MSIE 8.0
an hour ago, and only got 153600 bytes each time... try a better browser.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-
Andy Bradford wrote:
> Any chance you can use --httptrace when cloning with whatever is causing
> this problem? --httptrace will leave behind a handful of .txt files
> beginning with http- which have the requests and replies Fossil makes.
Problem not reproducible at the moment.
>> -rw-r--r--
Thus said Kelly Dean on Tue, 06 Jan 2015 21:03:03 +:
> That's horrible. You have to re-download the entire repository if one
> packet is lost at the end?
If you're suggesting that Fossil should treat network errors differently
during cloning and complete with whatever artifacts hav
Andy Bradford wrote:
> If the connection times out
> then I would expect the whole operation to fail and the repository be
> deleted.
That's horrible. You have to re-download the entire repository if one packet is
lost at the end?
> I'm curious what Fossil would do with one of the partial cl
Thus said Kelly Dean on Sun, 04 Jan 2015 04:21:55 +:
> Yesterday, the network probably dropped some packets. But it's
> misleading, at least for a new user, for Fossil to report that the
> clone finished when it actually didn't.
I have not been able to reproduce this problem. D
Yesterday I tried Fossil for the first time.
Using 1.29:
# fossil clone https://www.fossil-scm.org/ fossil-src.fossil
Round-trips: 2 Artifacts sent: 0 received: 3073
Clone finished with 3113 bytes sent, 1850717 bytes received
Rebuilding repository meta-data...
100.0% complete...
project-id:
a
15 matches
Mail list logo
