You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
go build -gcflags "-N -l"
...
gdb -d $(go env GOROOT) ./test-force
...
run
...
[Switching to Thread 0x7ffff67ee700 (LWP 5972)]
0x000000000060ee96 in github.com/nimajalali/go-force/force.(*ForceApi).GetSObject (
forceApi=0xc420058240, id=..., fields=..., out=..., err=...)
at /home/ubuntu/go/src/github.com/nimajalali/go-force/force/sobjects.go:75
75 uri := strings.Replace(forceApi.apiSObjects[out.ApiName()].URLs[rowTemplateKey], idKey, id, 1)
(gdb) info args
forceApi = 0xc420058240
id = 0x69a5e8 "Your-Object-ID"
fields = {array = 0x0, len = 0, cap = 0}
out = {tab = 0x7a4c40 <com/nimajalali/go-force/force.SObject>, data = 0xc4200188f0}
err = {tab = 0x699eb7, data = 0xc}
(gdb) info locals
value·3.len = 842350821952
uri.len = 0
v·1 = 0xc4200fdd50
value·3.ptr = 0x410b18 <runtime.newobject+56> "H\213D$\030H\211D$8H\213l$ H\203\304(\303\350\217\"\004"
uri.ptr = 0xb0 <error: Cannot access memory at address 0xb0>
(gdb)
I am quite happy of course that there will be no object with ID "Your-Object-ID"; and maybe the credentials I supplied are invalid (although they seem OK, e.g. if I alter the password I get an authentication error)
But either way, I don't think go-force should panic in this situation.
The text was updated successfully, but these errors were encountered:
force.ApiError{Fields:[]string(nil), Message:"Provided external ID field does not exist or is not accessible: Your-Object-ID", ErrorCode:"NOT_FOUND", ErrorName:"", ErrorDescription:""}
This is with Ubuntu 16.04 with the "official" go 1.8.1 distribution in
/usr/local/go
I am trying to run the example code at https://github.com/nimajalali/go-force/blob/master/README.md
Attempting to get a bit more info with gdb:
I am quite happy of course that there will be no object with ID "Your-Object-ID"; and maybe the credentials I supplied are invalid (although they seem OK, e.g. if I alter the password I get an authentication error)
But either way, I don't think go-force should panic in this situation.
The text was updated successfully, but these errors were encountered: