Closed agufagit closed 5 months ago
I'm not sure if it's related, but I also have issues when a process runs for a longer time on the same connection. I switched to 1.3.0 (due to an index creation bug), and then I also had to use the main commit as package version since Change was renamed to Patch and such. When I ran the older version 1.2.2 and the v0.2.1 tag, I had no issues completing this run. (It should insert about 3.5 mln docs.)
INFO[2024-03-14 00:23:05] processed 10000 elements caller="pkg/digest/digest.go:129" fName="/pkg/digest.(digestor).readFile" INFO[2024-03-14 00:24:06] processed 20000 elements caller="pkg/digest/digest.go:129" fName="/pkg/digest.(digestor).readFile" panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x2 addr=0x20 pc=0x10465c6d0] goroutine 34 [running]: github.com/surrealdb/surrealdb.go/pkg/conn/gorilla.(WebSocket).initialize.func1() /Users/sales/go/pkg/mod/github.com/surrealdb/surrealdb.go@v0.2.2-0.20240205063555-7c2584a964ab/pkg/conn/gorilla/gorilla.go:250 +0xa0 created by github.com/surrealdb/surrealdb.go/pkg/conn/gorilla.(WebSocket).initialize in goroutine 1 /Users/sales/go/pkg/mod/github.com/surrealdb/surrealdb.go@v0.2.2-0.20240205063555-7c2584a964ab/pkg/conn/gorilla/gorilla.go:238 +0x5c exit status 2
@agufagit, it would be helpful if you could test with the custom non-official SurrealDB Golang Driver that uses the nhooyr's websocket implementation instead of gorilla: non-official library. Please share the results. If it works with the custom driver, the issue might be related to the Gorilla toolkit.
@agufagit, it would be helpful if you could test with the custom non-official SurrealDB Golang Driver that uses the nhooyr's websocket implementation instead of gorilla: non-official library. Please share the results. If it works with the custom driver, the issue might be related to the Gorilla toolkit.
I'm using golang 1.22, it doesn't recognize your library in go.mod file
Describe the bug
got stack overflow error from gorilla websocket after idle for a while with db version 1.3.0
Steps to reproduce
idle for a while, an error is thrown from gorilla websocket
Expected behaviour
no error thrown
SurrealDB version
surreal 1.3.0
Contact Details
No response
Is there an existing issue for this?
Code of Conduct