Skip to content
New issue

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

ftl build warns repeatedly about connection refused #2002

Closed
matt2e opened this issue Jul 8, 2024 · 1 comment · Fixed by #2019
Closed

ftl build warns repeatedly about connection refused #2002

matt2e opened this issue Jul 8, 2024 · 1 comment · Fixed by #2019

Comments

@matt2e
Copy link
Collaborator

matt2e commented Jul 8, 2024

  • No FTL was running when I started.
  • ftl build --log-level=DEBUG in the ftl repo

Logs

debug: Unary RPC failed: unavailable: dial tcp [::1]:8892: connect: connection refused: /xyz.block.ftl.v1.AdminService/Ping
debug: Extracting dependencies for "echo"
debug: Extracting dependencies for "time"
debug: Unary RPC failed: unavailable: dial tcp [::1]:8892: connect: connection refused: /xyz.block.ftl.v1.ControllerService/GetSchema
debug: Failed to get schema from controller: unavailable: dial tcp [::1]:8892: connect: connection refused
debug: Extracting dependencies for "echo"
warn: Stream handler failed, retrying in 100ms: unavailable: dial tcp [::1]:8892: connect: connection refused
debug: Extracting dependencies for "time"
debug: Generating stubs for modules
warn: Stream handler failed, retrying in 200ms: unavailable: dial tcp [::1]:8892: connect: connection refused
debug: go: finding module for package github.com/TBD54566975/ftl/go-runtime/ftl
debug: go: found github.com/TBD54566975/ftl/go-runtime/ftl in github.com/TBD54566975/ftl v0.281.0
info:time: Building module
debug:time: Extracting schema
warn: Stream handler failed, retrying in 400ms: unavailable: dial tcp [::1]:8892: connect: connection refused
warn: Stream handler failed, retrying in 800ms: unavailable: dial tcp [::1]:8892: connect: connection refused
debug:time: Generating main module
debug:time: Tidying go.mod files
debug:time: go: found github.com/TBD54566975/ftl/backend/protos/xyz/block/ftl/v1/ftlv1connect in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:time: go: found github.com/TBD54566975/ftl/common/plugin in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:time: go: found github.com/TBD54566975/ftl/go-runtime/server in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:time: Compiling
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
info:time: Module built (2.22s)
debug: Generating stubs for modules
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
debug: go: finding module for package github.com/TBD54566975/ftl/go-runtime/ftl
debug: go: found github.com/TBD54566975/ftl/go-runtime/ftl in github.com/TBD54566975/ftl v0.281.0
info:echo: Building module
debug:echo: Extracting schema
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
debug:echo: Generating main module
debug:echo: Tidying go.mod files
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
debug:echo: go: found github.com/TBD54566975/ftl/backend/protos/xyz/block/ftl/v1/ftlv1connect in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:echo: go: found github.com/TBD54566975/ftl/common/plugin in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:echo: go: found github.com/TBD54566975/ftl/go-runtime/server in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:echo: Compiling
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
info:echo: Module built (2.79s)
@github-actions github-actions bot added the triage Issue needs triaging label Jul 8, 2024
@ftl-robot ftl-robot mentioned this issue Jul 8, 2024
jonathanj-square added a commit that referenced this issue Jul 9, 2024
unexpected warnings caused by retryable errors - retryable errors will continue to be reported as debug.
@github-actions github-actions bot removed the triage Issue needs triaging label Jul 9, 2024
@jonathanj-square
Copy link
Contributor

This is caused by my recent change that adds visibility to non-retryable rpc failures; the change added visibility to retryable ones as well by lifting their logging level from debug to warn.

jonathanj-square added a commit that referenced this issue Jul 10, 2024
unexpected warnings caused by retryable errors - retryable errors will continue to be reported as debug.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants