projectconfig.LoadOrCreate spamming the message "Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml"

[wesbillman]

When I run via the VSCode extension with --log-level=trace I see these messages filling the output window. This also seems to cause the CPU usage for ftl process to spike to 150% or so on my machine. Here's a snapshot of the output I see:

trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (unary)
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:func8: Running scheduled task
trace:func9: Running scheduled task
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (unary)
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (unary)
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml
trace:controller0: Loading config from /Users/wesbillman/dev/ftl/ftl-project.toml

I can also see a bunch of these messages when I run outside of VSCode (from terminal do ftl dev --recreate --log-level=trace):

trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)
trace:controller0: /xyz.block.ftl.v1.VerbService/GetModuleContext (streaming handler)

[safeer]

I'm seeing this when running ftl-controller, so it might be due to missing aws creds for asm?

debug:lease:/system/scheduledtask/reapStaleRunners: Acquired lease
warn: Unable to sync asm-leader: unable to get list of secrets from ASM: operation error Secrets Manager: ListSecrets, get identity: get credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, exceeded maximum number of attempts, 3, request send failed, Get "http://169.254.169.254/latest/meta-data/iam/security-credentials/": dial tcp 169.254.169.254:80: connect: host is down
debug: Streaming RPC failed: internal: could not get secrets: secrets not synced for asm-leader yet: /xyz.block.ftl.v1.VerbService/GetModuleContext
debug: Streaming RPC failed: internal: could not get secrets: secrets not synced for asm-leader yet: /xyz.block.ftl.v1.VerbService/GetModuleContext
debug: Streaming RPC failed: internal: could not get secrets: secrets not synced for asm-leader yet: /xyz.block.ftl.v1.VerbService/GetModuleContext
debug: Streaming RPC failed: internal: could not get secrets: secrets not synced for asm-leader yet: /xyz.block.ftl.v1.VerbService/GetModuleContext
debug: Streaming RPC failed: internal: could not get secrets: secrets not synced for asm-leader yet: /xyz.block.ftl.v1.VerbService/GetModuleContext
debug: Streaming RPC failed: internal: could not get secrets: secrets not synced for asm-leader yet: /xyz.block.ftl.v1.VerbService/GetModuleContext
debug: Streaming RPC failed: internal: could not get secrets: secrets not synced for asm-leader yet: /xyz.block.ftl.v1.VerbService/GetModuleContext

[wesbillman]

There was a bug recently that cause GetModuleContext to get called a bunch. I wonder if things are better now after that was fixed? Are you seeing this on the latest main @safeer ?