I have difficulty cloning libi0 as shown below.
-----
Sun Aug 30 17:29:07 CST 2015 lingu@worker3e5:/home/lingu/forest> cod clone libi0
The Ground is the directory where all the code trees reside.
The code tree will be cloned in the current Ground: /home/lingu/forest
Cloning into 'libi0'...
error: Failed connect to github.com:443; Connection timed out while accessing
https://github.com/layerzero/libi0/info/refs
fatal: HTTP request failed
-------
Seems a network problem:
In NB:
[zma@tb9-1 ~]$ git clone
https://github.com/layerzero/libi0/
Cloning into 'libi0'...
fatal: unable to access 'https://github.com/layerzero/libi0/': Failed connect to github.com:443; Connection timed out
In SZ:
[zma@gitliter ~]$ git clone
https://github.com/layerzero/libi0/
Cloning into libi0...
remote: Counting objects: 687, done.
remote: Total 687 (delta 0), reused 0 (delta 0), pack-reused 687
Receiving objects: 100% (687/687), 5.18 MiB | 155 KiB/s, done.
Resolving deltas: 100% (471/471), done.
In HK:
[zma@tb6-1 ~]$ git clone
https://github.com/layerzero/libi0/
Cloning into 'libi0'...
remote: Counting objects: 687, done.
remote: Total 687 (delta 0), reused 0 (delta 0), pack-reused 687
Receiving objects: 100% (687/687), 5.18 MiB | 59.00 KiB/s, done.
Resolving deltas: 100% (471/471), done.
Checking connectivity... done.
Perhaps it's time to move libi0 away from github as many users of D-thinker will be likely in mainland China.
(08-30-2015 10:33 PM)zma Wrote: [ -> ]Perhaps it's time to move libi0 away from github as many users of D-thinker will be likely in mainland China.
Let's wait a few days and see if things get better. If not we need to move it soon.
I tested to clone libi0 in NB, it takes around 2mins. Is this speed good for you?
Code:
[amoners@berners-lee code]$ time cod clone libi0
The Ground is the directory where all the code trees reside.
The code tree will be cloned in the current Ground: /home/amoners/forest
Cloning into 'libi0'...
remote: Counting objects: 694, done.
remote: Total 694 (delta 0), reused 0 (delta 0), pack-reused 694
Receiving objects: 100% (694/694), 5.33 MiB | 61.00 KiB/s, done.
Resolving deltas: 100% (477/477), done.
Checking connectivity... done.
real 2m3.611s
user 0m1.232s
sys 0m0.392s
(09-08-2015 03:47 PM)amoners Wrote: [ -> ]I tested to clone libi0 in NB, it takes around 2mins. Is this speed good for you?
Code:
[amoners@berners-lee code]$ time cod clone libi0
The Ground is the directory where all the code trees reside.
The code tree will be cloned in the current Ground: /home/amoners/forest
Cloning into 'libi0'...
remote: Counting objects: 694, done.
remote: Total 694 (delta 0), reused 0 (delta 0), pack-reused 694
Receiving objects: 100% (694/694), 5.33 MiB | 61.00 KiB/s, done.
Resolving deltas: 100% (477/477), done.
Checking connectivity... done.
real 2m3.611s
user 0m1.232s
sys 0m0.392s
Seems it is okay know to download libi0 in NB.
It is fine if it is a little bit slow. During deploying, the full history is not downloaded.
(09-08-2015 03:59 PM)zma Wrote: [ -> ] (09-08-2015 03:47 PM)amoners Wrote: [ -> ]I tested to clone libi0 in NB, it takes around 2mins. Is this speed good for you?
Code:
[amoners@berners-lee code]$ time cod clone libi0
The Ground is the directory where all the code trees reside.
The code tree will be cloned in the current Ground: /home/amoners/forest
Cloning into 'libi0'...
remote: Counting objects: 694, done.
remote: Total 694 (delta 0), reused 0 (delta 0), pack-reused 694
Receiving objects: 100% (694/694), 5.33 MiB | 61.00 KiB/s, done.
Resolving deltas: 100% (477/477), done.
Checking connectivity... done.
real 2m3.611s
user 0m1.232s
sys 0m0.392s
Seems it is okay know to download libi0 in NB.
It is fine if it is a little bit slow. During deploying, the full history is not downloaded.
It's a bit slow. I think most of the stuff in libi0 can naturally go to tc2/library since we already have such a dir anyway.