We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While calling Receive method on Subscription, getting below panic
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x16f0838] goroutine 6948 [running]: cloud.google.com/go/pubsub.(*pullStream).CloseSend.func1({0x0?, 0x0?}) cloud.google.com/go/[email protected]/pullstream.go:197 +0x18 cloud.google.com/go/pubsub.(*pullStream).call(0xc002936400, 0x37143c0, {0x0, 0x0, 0xc001527e58?}) cloud.google.com/go/[email protected]/pullstream.go:148 +0x144 cloud.google.com/go/pubsub.(*pullStream).CloseSend(0xc002936400) cloud.google.com/go/[email protected]/pullstream.go:196 +0x2a cloud.google.com/go/pubsub.(*messageIterator).sender.func1() cloud.google.com/go/[email protected]/iterator.go:396 +0x25 cloud.google.com/go/pubsub.(*messageIterator).sender(0xc007852100) cloud.google.com/go/[email protected]/iterator.go:479 +0x854 created by cloud.google.com/go/pubsub.newMessageIterator in goroutine 6944 cloud.google.com/go/[email protected]/iterator.go:152 +0x552
Can someone help with why such panic could be raised by pubsub library while getting messages from pubsub ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
While calling Receive method on Subscription, getting below panic
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x16f0838]
goroutine 6948 [running]:
cloud.google.com/go/pubsub.(*pullStream).CloseSend.func1({0x0?, 0x0?})
cloud.google.com/go/[email protected]/pullstream.go:197 +0x18
cloud.google.com/go/pubsub.(*pullStream).call(0xc002936400, 0x37143c0, {0x0, 0x0, 0xc001527e58?})
cloud.google.com/go/[email protected]/pullstream.go:148 +0x144
cloud.google.com/go/pubsub.(*pullStream).CloseSend(0xc002936400)
cloud.google.com/go/[email protected]/pullstream.go:196 +0x2a
cloud.google.com/go/pubsub.(*messageIterator).sender.func1()
cloud.google.com/go/[email protected]/iterator.go:396 +0x25
cloud.google.com/go/pubsub.(*messageIterator).sender(0xc007852100)
cloud.google.com/go/[email protected]/iterator.go:479 +0x854
created by cloud.google.com/go/pubsub.newMessageIterator in goroutine 6944
cloud.google.com/go/[email protected]/iterator.go:152 +0x552
Can someone help with why such panic could be raised by pubsub library while getting messages from pubsub ?
The text was updated successfully, but these errors were encountered: