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 console fails to load deployments #1578

Closed
mistermoe opened this issue May 27, 2024 · 0 comments · Fixed by #1591
Closed

ftl console fails to load deployments #1578

mistermoe opened this issue May 27, 2024 · 0 comments · Fixed by #1591
Assignees

Comments

@mistermoe
Copy link
Collaborator

ftl version: 0.226.0

image

There should be 10 deployments. no build or deployment errors when running ftl dev --recreate.

inspecting browser console shows:

image

Looks like the following request is failing:

❯ curl -v \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
'http://localhost:8892/xyz.block.ftl.v1.console.ConsoleService/GetModules' \
--data-raw '{}'
*   Trying [::1]:8892...
* connect to ::1 port 8892 failed: Connection refused
*   Trying 127.0.0.1:8892...
* Connected to localhost (127.0.0.1) port 8892
> POST /xyz.block.ftl.v1.console.ConsoleService/GetModules HTTP/1.1
> Host: localhost:8892
> User-Agent: curl/8.4.0
> Accept: application/json
> Content-Type: application/json
> Content-Length: 2
>
< HTTP/1.1 500 Internal Server Error
< Accept-Encoding: gzip
< Content-Type: application/json
< Date: Mon, 27 May 2024 22:40:10 GMT
< Content-Length: 53
<
* Connection #0 to host localhost left intact
{"code":"unknown","message":"failed to resolve Body"}%
@github-actions github-actions bot added the triage Issue needs triaging label May 27, 2024
@ftl-robot ftl-robot mentioned this issue May 27, 2024
@github-actions github-actions bot removed the triage Issue needs triaging label May 28, 2024
wesbillman added a commit that referenced this issue May 28, 2024
Fixes #1578 

We might want more protection around refs not being found, but I wasn't
sure how to make this allow for `TypeParameters` and also keep that
protection. This fix gets things working again, but we might want to
revisit this as well.
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