-
Notifications
You must be signed in to change notification settings - Fork 3
Closed
Description
when I run refrax refactor . --ai=deepseek, the refactoring proceeds successfully, however at the end I get the following error:
5:19PM INF critic: critic server stopped successfully
panic: failed to close resource: failed to stop fixer server: context deadline exceeded
panic: failed to close resource: failed to stop facilitator server: context deadline exceeded
goroutine 1 [running]:
github.com/cqfn/refrax/internal/client.closeResource({0x10620be0?, 0xc000020e60?})
/Users/lombrozo/Workspace/OpenSource/refrax/internal/client/refrax_client.go:189 +0x79
panic({0x1058b540?, 0xc000032bd0?})
/usr/local/Cellar/go/1.24.4/libexec/src/runtime/panic.go:792 +0x132
github.com/cqfn/refrax/internal/client.closeResource({0x10620c00?, 0xc000116300?})
/Users/lombrozo/Workspace/OpenSource/refrax/internal/client/refrax_client.go:189 +0x79
github.com/cqfn/refrax/internal/client.(*RefraxClient).Refactor(0xc0005adb10, {0x10620b60, 0xc0000327d0})
/Users/lombrozo/Workspace/OpenSource/refrax/internal/client/refrax_client.go:148 +0x130a
github.com/cqfn/refrax/internal/client.Refactor(0xc00017e1b0)
/Users/lombrozo/Workspace/OpenSource/refrax/internal/client/refrax_client.go:41 +0x153
github.com/cqfn/refrax/cmd.newRefactorCmd.func1(0xc000186200?, {0xc00018c3c0?, 0x4?, 0x1017e607?})
/Users/lombrozo/Workspace/OpenSource/refrax/cmd/refactor.go:25 +0x93
github.com/spf13/cobra.(*Command).execute(0xc00018a308, {0xc00018c360, 0x3, 0x3})
/Users/lombrozo/go/pkg/mod/github.com/spf13/[email protected]/command.go:1015 +0xaaa
github.com/spf13/cobra.(*Command).ExecuteC(0xc00018a008)
/Users/lombrozo/go/pkg/mod/github.com/spf13/[email protected]/command.go:1148 +0x46f
github.com/spf13/cobra.(*Command).Execute(...)
/Users/lombrozo/go/pkg/mod/github.com/spf13/[email protected]/command.go:1071
github.com/cqfn/refrax/cmd.Execute()
/Users/lombrozo/Workspace/OpenSource/refrax/cmd/root.go:13 +0x30
main.main()
/Users/lombrozo/Workspace/OpenSource/refrax/main.go:12 +0x13
Most probably it's some issue with incorrectly closed resources. We need to investigate the root cause of the issue.
Metadata
Metadata
Assignees
Labels
No labels