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

Config panic when running examples/go #1085

Closed
wesbillman opened this issue Mar 14, 2024 · 4 comments
Closed

Config panic when running examples/go #1085

wesbillman opened this issue Mar 14, 2024 · 4 comments
Labels
bug Something isn't working triage Issue needs triaging

Comments

@wesbillman
Copy link
Collaborator

This panic:

ftl serve --recreate
info: Starting FTL with 1 controller(s)
info:controller0: Web console available at: http://localhost:8892
info:controller0: Deployed time-79874598af
info:controller0: Deployed echo-827798ce84
error:echo: panic in verb echo.echo: failed to get {echo default}: no such key "default": not found

I'm running serve in one terminal and then in another terminal:

ftl deploy examples/go --log-level=debug

... followed by

ftl call echo.echo

Not sure if this is an issue with my setup, but wanted to record what I saw here since I mentioned it before.

@wesbillman wesbillman added the bug Something isn't working label Mar 14, 2024
@github-actions github-actions bot added the triage Issue needs triaging label Mar 14, 2024
@alecthomas
Copy link
Collaborator

I can't replicate this:

🐚 ~/dev/ftl $ ftl deploy examples/go
info:time: Building module
info:echo: Building module
info:time: Deploying module
info:echo: Deploying module
🐚 ~/dev/ftl $ ftl call echo.echo
{"message":"Hello, anonymous!!! It is 2024-03-15 06:52:27.282601 +1100 AEDT!"}

Are you starting ftl serve from the FTL repo? If you don't, it won't pick up the location of the ftl-project.toml file.

@wesbillman
Copy link
Collaborator Author

Yeah, all the commands were running from the FTL repo.

I'm also not able to repro on main currently. Maybe something was up with my local setup at the time, but wanted to record the error just in case since I saw it a couple times. Hopefully, a nothingburger.

@alecthomas
Copy link
Collaborator

Ah, no it was a bug but it was fixed yesterday.

@alecthomas
Copy link
Collaborator

In #1079

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Issue needs triaging
Projects
None yet
Development

No branches or pull requests

2 participants