drive push behavior is erratic when another .gd is present in any subfolder #829
Comments
|
I have the latest drive version installed: |
jean-christophe-manciot
changed the title
|
I have found what triggers that issue and I have to admit it should be a rare case. |
Introduce DebugPrintf which can be used to give
contextual and debug information when things go wrong
and we need to observe them, when verbose or `DEBUG=true`
is set in the environment.
So far added debugging prints when parsing the .driverc file.
It prints out the:
[<FILE>:<FUNCTION>:<LINE_NUMBER>]
Prefix a drive invocation with `DEBUG=true`
```shell
$ DEBUG=true drive list share-testing/
[/Users/emmanuelodeke/go/src/github.com/odeke-em/drive/cmd/drive/main.go:main.discoverContext:1857]
contextPath: /Users/emmanuelodeke/emm.odeke@gmail.com/share-testing
[/Users/emmanuelodeke/go/src/github.com/odeke-em/drive/cmd/drive/main.go:main.discoverContext:1867]
driveRoot: "/Users/emmanuelodeke/emm.odeke@gmail.com" relToRoot: ""
[/Users/emmanuelodeke/go/src/github.com/odeke-em/drive/src/rc.go:github.com/odeke-em/drive/src.ResourceMappings:92]
RCPath: /Users/emmanuelodeke/emm.odeke@gmail.com/share-testing/.driverc
[/Users/emmanuelodeke/go/src/github.com/odeke-em/drive/src/rc.go:github.com/odeke-em/drive/src.ResourceMappings:108]
parsedContent from
"/Users/emmanuelodeke/emm.odeke@gmail.com/share-testing/.driverc"
{
"global": {
"depth": -1
}
}
[Commands.List] #0 "/share-testing"
-- owner 175.00B 0Bwu8laYc9RTPa28zVk9Td2hTVWc 2016-06-30
15:32:25 +0000 UTC /share-testing/SciqPCKrhi.go
-- owner 309.00B 0Bwu8laYc9RTPTXRYblNqQXBSQzQ 2016-02-03
08:12:15 +0000 UTC /share-testing/outf.go
-s owner 39.70KB 0Bwu8laYc9RTPOVNSeElpdFBpS2M 2012-02-02
12:00:00 +0000 UTC /share-testing/ComedyPunchlineDrumSound.mp3
```
It will alleviate #829
since the reporter could then investigate and see the .gd path and
.driverc paths that were being read from.
|
@jean-christophe-manciot thanks for reporting this. So if you put a .gd file in any directory, that makes that directory the root. That means therefore that if you make a push operation, then it will be relative to that root. Unfortunately in the past there was no where to debug that information. [/Users/emmanuelodeke/go/src/github.com/odeke-em/drive/cmd/drive/main.go:main.discoverContext:1857]
contextPath: "/Users/emmanuelodeke/emm.odeke@gmail.com/share-testing"
[/Users/emmanuelodeke/go/src/github.com/odeke-em/drive/cmd/drive/main.go:main.discoverContext:1867]
driveRoot: "/Users/emmanuelodeke/emm.odeke@gmail.com" relToRoot: ""
[/Users/emmanuelodeke/go/src/github.com/odeke-em/drive/src/rc.go:github.com/odeke-em/drive/src.ResourceMappings:92]
RCPath: /Users/emmanuelodeke/emm.odeke@gmail.com/.driverc
[/Users/emmanuelodeke/go/src/github.com/odeke-em/drive/src/rc.go:github.com/odeke-em/drive/src.ResourceMappings:108]
parsedContent from "/Users/emmanuelodeke/emm.odeke@gmail.com/.driverc" |
|
Shouldn't it stop at the first found .gd folder? |
I know how this sounds, it is a strange issue. I'm as surprised as I guess you are.
Here is the situation:
Now, the issue: I'm just trying to push the folder "Test" with an infinite depth (-1).
The result does not make any sense:
It does not make sense because:
My suspicion goes to the fact that my local GD root folder has a space within (Google Drive) which seems to completely disorient drive.
The local symlinks may also confuse drive.
The text was updated successfully, but these errors were encountered: