Skip to content

Getting "connection refused" after apparently successful contract PUT with fdev #1465

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
sanity opened this issue Mar 10, 2025 · 3 comments
Closed
Assignees

Comments

@sanity
Copy link
Collaborator

sanity commented Mar 10, 2025

This happens consistently but it doesn't seem to prevent the contract from being PUT successfully.

[cargo-make] INFO - Running Task: publish-river-debug
Publishing using committed contract in debug mode: C8tm2U616vC2dBo8ffWoc8YL9yJGyKJ5C4Y2Nfm2YAn5
  2025-03-10T15:10:09.806390Z  INFO fdev::commands: Metadata being packed into WebApp state, metadata_len: 146
    at crates/fdev/src/commands.rs:120

  2025-03-10T15:10:09.806435Z  INFO fdev::commands: First 32 bytes of metadata, first_32_bytes: "[a2, 67, 76, 65, 72, 73, 69, 6f, 6e, 1a, 01, ba, ea, ae, 69, 73, 69, 67, 6e, 61, 74, 75, 72, 65, 98, 40, 18, da, 18, f8, 18, 5d]"
    at crates/fdev/src/commands.rs:125

  2025-03-10T15:10:09.807941Z  INFO fdev::commands: WebApp state after packing, packed_len: 2062106
    at crates/fdev/src/commands.rs:131

  2025-03-10T15:10:09.807955Z  INFO fdev::commands: First 32 bytes of packed state, first_32_bytes: "[00, 00, 00, 00, 00, 00, 00, 92, a2, 67, 76, 65, 72, 73, 69, 6f, 6e, 1a, 01, ba, ea, ae, 69, 73, 69, 67, 6e, 61, 74, 75, 72, 65]"
    at crates/fdev/src/commands.rs:136

Publishing contract C8tm2U616vC2dBo8ffWoc8YL9yJGyKJ5C4Y2Nfm2YAn5
  2025-03-10T15:10:09.810220Z ERROR fdev::commands::v1: err: IO error: Connection refused (os error 111)
    at crates/fdev/src/commands/v1.rs:24

Error: fail to connect to the host(127.0.0.1:50509): IO error: Connection refused (os error 111)
Error while executing command, exit code: 1
@sanity sanity moved this to Triage in Freenet Core Mar 10, 2025
@iduartgomez
Copy link
Collaborator

This is with fdev no? We are not handling closing connections gracefully.

@iduartgomez
Copy link
Collaborator

iduartgomez commented Mar 16, 2025

Fixed in #1473 (probably, can you double check)

@sanity
Copy link
Collaborator Author

sanity commented Mar 17, 2025

Haven't seen this recently so closing, thank you!

@sanity sanity closed this as completed Mar 17, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants