Storage example script panics

Bug #1213059 reported by Raphaël Badin on 2013-08-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Go Windows Azure Client Library
Critical
Jeroen T. Vermeulen

Bug Description

example/storage/run.go panics when trying to set access on a container:

$ go run example/storage/run.go -account=myaccount -container=mycontainer container -key mykey containeracl
panic: no AzureEndpoint specified in gwacl.StorageContext

goroutine 1 [running]:
launchpad.net/gwacl.(*StorageContext).getAccountURL(0xc2000ca0c0, 0xc2000adb38, 0xc2000adae0)
 /home/rvb/canonical/go/src/launchpad.net/gwacl/storage_base.go:337 +0xa6
launchpad.net/gwacl.(*StorageContext).getContainerURL(0xc2000ca0c0, 0x7fff8094737d, 0x4, 0x40ab4d, 0x5e5d00, ...)
 /home/rvb/canonical/go/src/launchpad.net/gwacl/storage_base.go:345 +0x25
launchpad.net/gwacl.(*StorageContext).SetContainerACL(0xc2000ca0c0, 0xc2000b3720, 0xc, 0x6b7070)
 /home/rvb/canonical/go/src/launchpad.net/gwacl/storage_base.go:703 +0x4a
main.containeracl(0x7fff8094735a, 0x17, 0x7fff80947396, 0x58, 0x0, ...)
 /home/rvb/canonical/go/src/launchpad.net/gwacl/example/storage/run.go:194 +0x99
main.main()
 /home/rvb/canonical/go/src/launchpad.net/gwacl/example/storage/run.go:301 +0x34c

goroutine 2 [runnable]:
exit status 2

I suspect the script has not been updated to cope with the fact that specifying an AzureEndpoint is now mandatory. Maybe I'm wrong and I've given it wrong arguments. In any case, the script shouldn't panic.

Related branches

Changed in gwacl:
importance: Low → Critical
Changed in gwacl:
assignee: nobody → Jeroen T. Vermeulen (jtv)
status: Triaged → In Progress
Changed in gwacl:
status: In Progress → Fix Committed
Curtis Hovey (sinzui) on 2013-12-10
Changed in gwacl:
milestone: none → 0.1.1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers