You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WARN[2024-08-09T15:16:22+08:00] You are running an old version of the Kurtosis CLI; we suggest you to update it to the latest version, '1.0.0'. You can manually upgrade the CLI tool following these instructions: https://docs.kurtosis.com/upgrade
✅ kurtosis 0.89.11 is installed, meets the requirement (=0.89).
✅ docker 26.0.0 is installed, meets the requirement (>=24.7).
You might as well need the following tools to interact with the environment...
✅ jq 1.6 is installed.
⚠️ yq is not installed. You can install yq at: https://pypi.org/project/yq/
✅ cast 0.2.0 is installed.
⚠️ polycli is not installed. You can install polycli at: https://github.com/maticnetwork/polygon-cli/releases
🎉 You are ready to go!
Previously, every deploy was successful, but zkEVM bridge deposit has been unable to be credited. But recently, there is a high probability that I will encounter ```fea2scalar errors`` during every deploy.
What is the severity of this bug?
Critical; I am blocked and Kurtosis CDK is unusable for me because of this bug.
The text was updated successfully, but these errors were encountered:
System information
Ubuntu22.04 - amd64
Commit id
b231b01
Tools versions
Description & steps to reproduce
Starting bridge infra
There was an error executing Starlark code
An error occurred executing instruction (number 38) at github.com/0xPolygon/kurtosis-cdk/cdk_bridge_infra.star[38:46]:
add_services(configs={"zkevm-agglayer-001": ServiceConfig(image="ghcr.io/agglayer/agglayer-rs:main", ports={"agglayer": PortSpec(number=4444, application_protocol="http"), "prometheus": PortSpec(number=9091, application_protocol="http")}, public_ports={"agglayer": PortSpec(number=18084, application_protocol="http")}, files={"/etc/zkevm": Directory(artifact_names=["agglayer-config-artifact", "agglayer-keystore"])}, entrypoint=["/usr/local/bin/agglayer"], cmd=["run", "--cfg", "/etc/zkevm/agglayer-config.toml"]), "zkevm-bridge-service-001": ServiceConfig(image="hermeznetwork/zkevm-bridge-service:v0.4.2", ports={"grpc": PortSpec(number=9090, application_protocol="grpc"), "rpc": PortSpec(number=8080, application_protocol="http")}, public_ports={"grpc": PortSpec(number=18083, application_protocol="grpc"), "rpc": PortSpec(number=18082, application_protocol="http")}, files={"/etc/zkevm": Directory(artifact_names=["bridge-config-artifact", "claimtxmanager-keystore"])}, entrypoint=["/app/zkevm-bridge"], cmd=["run", "--cfg", "/etc/zkevm/bridge-config.toml"])}, description="Starting bridge infra")
Caused by: Some errors occurred starting or updating the following services: '[zkevm-bridge-service-001]'. The entire batch was rolled back an no service was started. Errors were:
Service creations: map[zkevm-bridge-service-001:An error occurred waiting for all TCP and UDP ports to be open for service 'zkevm-bridge-service-001' with private IP '172.16.0.17'; this is usually due to a misconfiguration in the service itself, so here are the logs:
== SERVICE 'zkevm-bridge-service-001' LOGS ===================================
{"level":"info","ts":1723175647.2737653,"caller":"pgstorage/utils.go:63","msg":"successfully ran 8 migrations","pid":7,"version":"v0.4.2"}
{"level":"info","ts":1723175647.2876232,"caller":"cmd/run.go:57","msg":"main network id: 0","pid":7,"version":"v0.4.2"}
{"level":"error","ts":1723175647.313141,"caller":"cmd/run.go:67","msg":"failed to execute the unsigned transaction: fea2scalar error\n/src/log/log.go:142 github.com/0xPolygonHermez/zkevm-bridge-service/log.appendStackTraceMaybeArgs()\n/src/log/log.go:217 github.com/0xPolygonHermez/zkevm-bridge-service/log.Error()\n/src/cmd/run.go:67 main.start()\n/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:277 github.com/urfave/cli/v2.(*Command).Run()\n/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:270 github.com/urfave/cli/v2.(*Command).Run()\n/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:335 github.com/urfave/cli/v2.(*App).RunContext()\n/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:309 github.com/urfave/cli/v2.(*App).Run()\n/src/cmd/main.go:56 main.main()\n/usr/local/go/src/runtime/proc.go:267 runtime.main()\n","pid":7,"version":"v0.4.2","stacktrace":"main.start\n\t/src/cmd/run.go:67[ngithub.com/urfave/cli/v2.(*Command).Run\n\t/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:277\ngithub.com/urfave/cli/v2.(*Command).Run\n\t/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:270\ngithub.com/urfave/cli/v2.(*App).RunContext\n\t/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:335\ngithub.com/urfave/cli/v2.(*App).Run\n\t/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:309\nmain.main\n\t/src/cmd/main.go:56\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:267](http://ngithub.com/urfave/cli/v2.(*Command).Run/n/t/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:277/ngithub.com/urfave/cli/v2.(*Command).Run/n/t/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:270/ngithub.com/urfave/cli/v2.(*App).RunContext/n/t/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:335/ngithub.com/urfave/cli/v2.(*App).Run/n/t/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:309/nmain.main/n/t/src/cmd/main.go:56/nruntime.main/n/t/usr/local/go/src/runtime/proc.go:267)"}
Error: failed to execute the unsigned transaction: fea2scalar error
Desired behavior
#163 (comment)
Previously, every deploy was successful, but zkEVM bridge deposit has been unable to be credited. But recently, there is a high probability that I will encounter ```fea2scalar errors`` during every deploy.
What is the severity of this bug?
Critical; I am blocked and Kurtosis CDK is unusable for me because of this bug.
The text was updated successfully, but these errors were encountered: