Skip to content
This repository has been archived by the owner on Oct 19, 2019. It is now read-only.

v8 did not contain fe12316e... #9

Open
terasum opened this issue Jun 6, 2018 · 1 comment
Open

v8 did not contain fe12316e... #9

terasum opened this issue Jun 6, 2018 · 1 comment

Comments

@terasum
Copy link

terasum commented Jun 6, 2018

when I clone the v8worker2 code, and get the submodule, it failed with:

> git submodule update --init --recursive 

Cloning into '/home/xxx/Workspace/go/src/github.com/ry/v8worker2/depot_tools'...
Cloning into '/home/xxx/Workspace/go/src/github.com/ry/v8worker2/v8'...
remote: Counting objects: 26439, done
remote: Finding sources: 100% (26439/26439)
remote: Total 26439 (delta 16997), reused 26425 (delta 16997)
Receiving objects: 100% (26439/26439), 32.11 MiB | 5.99 MiB/s, done.
Resolving deltas: 100% (16997/16997), done.
From https://chromium.googlesource.com/chromium/tools/depot_tools
 * branch              f16fdf3165b8b86d10386d18a6b6075169c10e15 -> FETCH_HEAD
Submodule path 'depot_tools': checked out 'f16fdf3165b8b86d10386d18a6b6075169c10e15'
error: no such remote ref fe12316ec4b4a101923e395791ca55442e62f4cc
Fetched in submodule path 'v8', but it did not contain fe12316ec4b4a101923e395791ca55442e62f4cc. Direct fetching of that commit failed.

how to fix this?

thanks very much!
@terasum
Copy link
Author

terasum commented Jun 6, 2018

I try to fix this by:

cd $GOPATH/src/github.com/ry/v8worker2
rm -rf v8
git clone https://github.com/v8/v8.git
cd v8 
git checkout fe12316ec4b4a101923e395791ca55442e62f4cc

and finally, it can find the fe12316ec4...

HEAD is now at fe12316ec4... Version 6.8.275.3

does this correct?

@terasum terasum mentioned this issue Jun 6, 2018
Closed
dlespiau added a commit to jkcfg/v8worker2 that referenced this issue Nov 2, 2018
@dlespiau
Remove branch in v8 submodule
ceb9268 
I suspect this is the cause of:

Submodule 'depot_tools' (https://chromium.googlesource.com/chromium/tools/depot_tools.git) registered for path 'depot_tools'
Submodule 'v8' (https://github.com/v8/v8.git) registered for path 'v8'
Cloning into '/go/src/github.com/ry/v8worker2/depot_tools'...
Cloning into '/go/src/github.com/ry/v8worker2/v8'...
From https://chromium.googlesource.com/chromium/tools/depot_tools
 * branch              f16fdf3165b8b86d10386d18a6b6075169c10e15 -> FETCH_HEAD
error: no such remote ref fe12316ec4b4a101923e395791ca55442e62f4cc
Fetched in submodule path 'v8', but it did not contain fe12316ec4b4a101923e395791ca55442e62f4cc. Direct fetching of that commit failed.
package github.com/ry/v8worker2: exit status 1

Fixes: ry#9
dlespiau added a commit to jkcfg/v8worker2 that referenced this issue Nov 2, 2018
@dlespiau
Remove branch in v8 submodule
18122a3 
I suspect this is the cause of:

Submodule 'depot_tools' (https://chromium.googlesource.com/chromium/tools/depot_tools.git) registered for path 'depot_tools'
Submodule 'v8' (https://github.com/v8/v8.git) registered for path 'v8'
Cloning into '/go/src/github.com/ry/v8worker2/depot_tools'...
Cloning into '/go/src/github.com/ry/v8worker2/v8'...
From https://chromium.googlesource.com/chromium/tools/depot_tools
 * branch              f16fdf3165b8b86d10386d18a6b6075169c10e15 -> FETCH_HEAD
error: no such remote ref fe12316ec4b4a101923e395791ca55442e62f4cc
Fetched in submodule path 'v8', but it did not contain fe12316ec4b4a101923e395791ca55442e62f4cc. Direct fetching of that commit failed.
package github.com/ry/v8worker2: exit status 1

Fixes: ry#9
dlespiau added a commit to jkcfg/v8worker2 that referenced this issue Nov 2, 2018
@dlespiau
Remove branch in v8 submodule
02469cd 
I suspect this is the cause of:

Submodule 'depot_tools' (https://chromium.googlesource.com/chromium/tools/depot_tools.git) registered for path 'depot_tools'
Submodule 'v8' (https://github.com/v8/v8.git) registered for path 'v8'
Cloning into '/go/src/github.com/ry/v8worker2/depot_tools'...
Cloning into '/go/src/github.com/ry/v8worker2/v8'...
From https://chromium.googlesource.com/chromium/tools/depot_tools
 * branch              f16fdf3165b8b86d10386d18a6b6075169c10e15 -> FETCH_HEAD
error: no such remote ref fe12316ec4b4a101923e395791ca55442e62f4cc
Fetched in submodule path 'v8', but it did not contain fe12316ec4b4a101923e395791ca55442e62f4cc. Direct fetching of that commit failed.
package github.com/ry/v8worker2: exit status 1

Fixes: ry#9
dlespiau added a commit to jkcfg/v8worker2 that referenced this issue Nov 2, 2018
@dlespiau
Don't use shallow clones for v8 and update the submodule branch
056c20b 
The shallow setting this is the cause of:

Submodule 'depot_tools' (https://chromium.googlesource.com/chromium/tools/depot_tools.git) registered for path 'depot_tools'
Submodule 'v8' (https://github.com/v8/v8.git) registered for path 'v8'
Cloning into '/go/src/github.com/ry/v8worker2/depot_tools'...
Cloning into '/go/src/github.com/ry/v8worker2/v8'...
From https://chromium.googlesource.com/chromium/tools/depot_tools
 * branch              f16fdf3165b8b86d10386d18a6b6075169c10e15 -> FETCH_HEAD
error: no such remote ref fe12316ec4b4a101923e395791ca55442e62f4cc
Fetched in submodule path 'v8', but it did not contain fe12316ec4b4a101923e395791ca55442e62f4cc. Direct fetching of that commit failed.
package github.com/ry/v8worker2: exit status 1

Current theory is that shallow clones aren't enough to find the right commit,
even when specifying the right branch to look for it.

So:

- Don't use shallow clones
- Specify the right branch where to find 6.8 releases, this should help when
  updating the submodule if one wants to follow the 6.8.x.y releases.

Fixes: ry#9
dlespiau added a commit to jkcfg/v8worker2 that referenced this issue Nov 2, 2018
@dlespiau
Don't use shallow clones for v8 and update the submodule branch
0d33c87 
The shallow setting this is the cause of:

Submodule 'depot_tools' (https://chromium.googlesource.com/chromium/tools/depot_tools.git) registered for path 'depot_tools'
Submodule 'v8' (https://github.com/v8/v8.git) registered for path 'v8'
Cloning into '/go/src/github.com/ry/v8worker2/depot_tools'...
Cloning into '/go/src/github.com/ry/v8worker2/v8'...
From https://chromium.googlesource.com/chromium/tools/depot_tools
 * branch              f16fdf3165b8b86d10386d18a6b6075169c10e15 -> FETCH_HEAD
error: no such remote ref fe12316ec4b4a101923e395791ca55442e62f4cc
Fetched in submodule path 'v8', but it did not contain fe12316ec4b4a101923e395791ca55442e62f4cc. Direct fetching of that commit failed.
package github.com/ry/v8worker2: exit status 1

Current theory is that shallow clones aren't enough to find the right commit,
even when specifying the right branch to look for it.

So:

- Don't use shallow clones
- Specify the right branch where to find 6.8 releases, this should help when
  updating the submodule if one wants to follow the 6.8.x.y releases.

Fixes: ry#9
dlespiau added a commit to jkcfg/v8worker2 that referenced this issue Nov 2, 2018
@dlespiau
Don't use shallow clones for update the v8 submodule branch
6afdcbe 
The shallow setting this is the cause of those two errors:

Submodule 'depot_tools' (https://chromium.googlesource.com/chromium/tools/depot_tools.git) registered for path 'depot_tools'
Submodule 'v8' (https://github.com/v8/v8.git) registered for path 'v8'
Cloning into '/go/src/github.com/ry/v8worker2/depot_tools'...
Cloning into '/go/src/github.com/ry/v8worker2/v8'...
From https://chromium.googlesource.com/chromium/tools/depot_tools
 * branch              f16fdf3165b8b86d10386d18a6b6075169c10e15 -> FETCH_HEAD
error: no such remote ref fe12316ec4b4a101923e395791ca55442e62f4cc
Fetched in submodule path 'v8', but it did not contain fe12316ec4b4a101923e395791ca55442e62f4cc. Direct fetching of that commit failed.
package github.com/ry/v8worker2: exit status 1

and:

depot_tools update failed. Conflict in /go/src/github.com/dlespiau/v8worker2/depot_tools

Current theory is that shallow clones aren't enough to find the right commit,
even when specifying the right branch to look for it.

So:

- Don't use shallow clones
- Specify the right branch where to find 6.8 releases, this should help when
  updating the submodule if one wants to follow the 6.8.x.y releases.

Fixes: ry#9
dlespiau added a commit to jkcfg/v8worker2 that referenced this issue Nov 2, 2018
@dlespiau
Don't use shallow clones for update the v8 submodule branch
32490fd 
The shallow setting this is the cause of those two errors:

Submodule 'depot_tools' (https://chromium.googlesource.com/chromium/tools/depot_tools.git) registered for path 'depot_tools'
Submodule 'v8' (https://github.com/v8/v8.git) registered for path 'v8'
Cloning into '/go/src/github.com/ry/v8worker2/depot_tools'...
Cloning into '/go/src/github.com/ry/v8worker2/v8'...
From https://chromium.googlesource.com/chromium/tools/depot_tools
 * branch              f16fdf3165b8b86d10386d18a6b6075169c10e15 -> FETCH_HEAD
error: no such remote ref fe12316ec4b4a101923e395791ca55442e62f4cc
Fetched in submodule path 'v8', but it did not contain fe12316ec4b4a101923e395791ca55442e62f4cc. Direct fetching of that commit failed.
package github.com/ry/v8worker2: exit status 1

and:

depot_tools update failed. Conflict in /go/src/github.com/dlespiau/v8worker2/depot_tools

Current theory is that shallow clones aren't enough to find the right commit,
even when specifying the right branch to look for it.

So:

- Don't use shallow clones
- Specify the right branch where to find 6.8 releases, this should help when
  updating the submodule if one wants to follow the 6.8.x.y releases.

Fixes: ry#9
dlespiau added a commit to jkcfg/v8worker2 that referenced this issue Nov 2, 2018
@dlespiau
Don't use shallow clones for update the v8 submodule branch
722c981 
The shallow setting this is the cause of those two errors:

Submodule 'depot_tools' (https://chromium.googlesource.com/chromium/tools/depot_tools.git) registered for path 'depot_tools'
Submodule 'v8' (https://github.com/v8/v8.git) registered for path 'v8'
Cloning into '/go/src/github.com/ry/v8worker2/depot_tools'...
Cloning into '/go/src/github.com/ry/v8worker2/v8'...
From https://chromium.googlesource.com/chromium/tools/depot_tools
 * branch              f16fdf3165b8b86d10386d18a6b6075169c10e15 -> FETCH_HEAD
error: no such remote ref fe12316ec4b4a101923e395791ca55442e62f4cc
Fetched in submodule path 'v8', but it did not contain fe12316ec4b4a101923e395791ca55442e62f4cc. Direct fetching of that commit failed.
package github.com/ry/v8worker2: exit status 1

and:

depot_tools update failed. Conflict in /go/src/github.com/dlespiau/v8worker2/depot_tools

Current theory is that shallow clones aren't enough to find the right commit
(for the v8 issue that is), even when specifying the right branch to look for
it.

So:

- Don't use shallow clones
- Specify the right branch where to find 6.8 releases, this should help when
  updating the submodule if one wants to follow the 6.8.x.y releases.

Fixes: ry#9
@dlespiau dlespiau mentioned this issue Nov 2, 2018
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@terasum