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
panic: runtime error: integer divide by zero
goroutine 97 [running]:
github.com/hypermodeinc/dgraph/v24/worker.(*groupi).connToZeroLeader(0x1064dc1e0)
/Users/matthew/go/pkg/mod/github.com/hypermodeinc/dgraph/[email protected]/worker/groups.go:738 +0x374
github.com/hypermodeinc/dgraph/v24/worker.(*groupi).BelongsToReadOnly(0x1064dc1e0, {0x1400053c120, 0xd}, 0x2)
/Users/matthew/go/pkg/mod/github.com/hypermodeinc/dgraph/[email protected]/worker/groups.go:440 +0x164
github.com/hypermodeinc/dgraph/v24/worker.ProcessTaskOverNetwork({0x1058a1718, 0x1400031e330}, 0x14000494000)
/Users/matthew/go/pkg/mod/github.com/hypermodeinc/dgraph/[email protected]/worker/task.go:137 +0x54
github.com/hypermodeinc/dgraph/v24/query.ProcessGraph({0x1058a1718, 0x1400031e330}, 0x1400051a908, 0x0, 0x1400069caf0)
/Users/matthew/go/pkg/mod/github.com/hypermodeinc/dgraph/[email protected]/query/query.go:2170 +0x870
created by github.com/hypermodeinc/dgraph/v24/query.(*Request).ProcessQuery in goroutine 1
/Users/matthew/go/pkg/mod/github.com/hypermodeinc/dgraph/[email protected]/query/query.go:2884 +0xaa8
Expected behavior
Should be able to query for a non-existent type and have it return a not-found error
Additional Context
I believe this is because there's no schema applied before this query. And the worker is trying to find the group the predicates belong to.
Environment
OS: macOS
Language Go
The text was updated successfully, but these errors were encountered:
Update, this is only happening with the modusdb.ConstrainedField option. The standard gid search returns "object not found" correctly.
matthewmcneely
changed the title
Querying for non-existent record in db panics
Querying for non-existent record by constrained field panics
Feb 20, 2025
Describe the bug
Querying for non-existent record panics in worker
To Reproduce
Expected behavior
Should be able to query for a non-existent type and have it return a not-found error
Additional Context
I believe this is because there's no schema applied before this query. And the worker is trying to find the group the predicates belong to.
Environment
The text was updated successfully, but these errors were encountered: