google/comprehensive-rust

Include instructions for connecting to server in Tasks example

Open

#1,349 opened on Oct 11, 2023

View on GitHub
 (6 comments) (0 reactions) (1 assignee)Rust (32,954 stars) (2,009 forks)batch import
good first issue

Description

Discussed in https://github.com/google/comprehensive-rust/discussions/1316

Originally posted by njr0 October 6, 2023 .. I made it run OK (by just adding tokio = { version = "1.32.0", features = ["full"] } as a dependency in Cargo.toml, and I could get it to say connection from 127.0.0.1:64382 etc. by using curl, but I guess I'd have to write code to connect to the socket and receive the question and send a reply and stuff. Presumably, that's what's in the "prepared main.rs. ..

nc or telnet are good tools for this. It's not HTTPS, so curl's not a good choice.

This should be mentioned in the speaker notes.

Contributor guide

Tech stack
rust
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
This issue requests adding instructions in the speaker notes for the Tasks example to use `nc` or `telnet` to connect to the server, as discussed in the linked discussion. The change is likely in the course material's Markdown files, such as the speaker notes for the relevant section. The maintainer should add a brief note explaining that curl is not suitable and that nc or telnet can be used for testing the server.