Example code only seems to work if I change the server to use ipv4

[CaliViking]

Example code only seems to work if I change the server to use ipv4

[tikue]

Nice! RUST_LOG is not specific to tarpc, but it would still be good for the tarpc examples that use it to specify how to get output :)

[tikue]

Thanks for the report! That's interesting — I can't reproduce this problem on my Macbook, but I can't say you're doing anything wrong either! At least, not without a bit more info :)

• What's the specific error you're getting? Is it something like invalid IP address syntax?
• Can you try --server-addr '[::1]:59061'?

[ha-sante]

Same experience on end. Would add using the tarpc module feels like working in the dark as there is no logs you can tap into.

• Documentation can be incredibly better for launching a tcp transport server.
• Logs can be better for the dev experience.
• Example service doesn't tell you anything on fresh launch(execute client bin and it dosen't get a response log).

Still exploring for my use case and haven't managed to make an RPC call for 2 days now with pure pull from the example service.

Sorry.

Will contribute to making things better when am able to successfully make use of it and it's associated features. - A big blocker to contributions.
Sorry.

[tikue]

Hi, I'm sorry you've had a frustrating experience! Feel free to join the discord channel where others might help fix your problems faster.

There should be some logs available for the client binary, not sure what's going wrong. Have you enabled log output with RUST_LOG environment variable? E.g. RUST_LOG=debug cargo run --bin client?

[ha-sante]

F##k yeah, it finally logged. Your command did it.

Would this be my knowledge of rust or it's how you get debug information from your setup?

- I learned rust much more fully a few days ago hence my curiosity

Most helpful thing I will do now is to write a beginners guide once am up to speed with what am doing.

[ha-sante]

Can see, my memory bank needs an update. Thanks for the insight.