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
invalid memory address or nil pointer dereference
oCIS crashed twice in web ci pipeline.
builds:
ocis commit: c7a3ec2
+ ./ocis server 2024/07/23 06:31:22 INFO memory is not limited, skipping package=github.com/KimMachineGun/automemlimit/memlimit panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0xa8 pc=0xf1c4c2] goroutine 33 [running]: github.com/go-micro/plugins/v4/store/nats-js-kv.(*natsStore).WatchAll(0x6a6e8a0?, {0x354b8c8?, 0x8?}, {0x0, 0x0, 0x0}) /var/www/owncloud/web/repo_ocis/vendor/github.com/go-micro/plugins/v4/store/nats-js-kv/nats.go:344 +0xa2 github.com/owncloud/ocis/v2/ocis-pkg/natsjsregistry.NewWatcher(0xc000ad2ea0) /var/www/owncloud/web/repo_ocis/ocis-pkg/natsjsregistry/watcher.go:29 +0x65 github.com/owncloud/ocis/v2/ocis-pkg/natsjsregistry.(*storeregistry).Watch(0x64?, {0xc00080eb40?, 0x3572ae9?, 0x18?}) /var/www/owncloud/web/repo_ocis/ocis-pkg/natsjsregistry/registry.go:136 +0x13 go-micro.dev/v4/registry/cache.(*cache).run(0xc000ad2f30, {0x3572ae9, 0x18}) /var/www/owncloud/web/repo_ocis/vendor/go-micro.dev/v4/registry/cache/cache.go:348 +0x1f9 created by go-micro.dev/v4/registry/cache.(*cache).get in goroutine 1 /var/www/owncloud/web/repo_ocis/vendor/go-micro.dev/v4/registry/cache/cache.go:186 +0x2e5
The text was updated successfully, but these errors were encountered:
Issue with nats-js store. Will file a fix today.
Sorry, something went wrong.
kobergj
Successfully merging a pull request may close this issue.
oCIS crashed twice in web ci pipeline.
builds:
ocis commit: c7a3ec2
The text was updated successfully, but these errors were encountered: