rust/comprehensive-rust
1
0
Fork 0
mirror of https://github.com/google/comprehensive-rust.git synced 2024-12-14 14:10:05 +02:00
Code Issues Releases Activity
36449cb1b2
comprehensive-rust/Cargo.lock

2730 lines
66 KiB
Plaintext
Raw Normal View History

Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "addr2line"
version = "0.21.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8a30b2e23b9e17a9f90641c7ab1549cd9b44f296d3ccbf309d2863cfe398a0cb"
dependencies = [
"gimli",
]
[[package]]
name = "adler"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "aho-corasick"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.5"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "0c378d78423fdad8089616f827526ee33c19f2fddbd5de1629152c9593ba4783"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
dependencies = [
"memchr",
]
Add page about buddy_system_allocator.
2023-03-16 20:07:58 +02:00
[[package]]
name = "allocator-example"
version = "0.1.0"
dependencies = [
"buddy_system_allocator",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "ammonia"
version = "3.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "64e6d1c7838db705c9b756557ee27c384ce695a1c51a6fe528784cb1c6840170"
dependencies = [
"html5ever",
"maplit",
"once_cell",
"tendril",
"url",
]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "android-tzdata"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e999941b234f3131b00bc13c22d06e8c5ff726d1b6318ac7eb276997bbb4fef0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "android_system_properties"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "819e7219dbd41043ac279b19830f2efc897156490d7fd6ea916720117ee66311"
dependencies = [
"libc",
]
[[package]]
name = "anstream"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.5.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "b1f58811cfac344940f1a400b6e6231ce35171f614f26439e80f8c1465c5cc0c"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"anstyle",
"anstyle-parse",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"anstyle-query",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"anstyle-wincon",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"colorchoice",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"utf8parse",
]
[[package]]
name = "anstyle"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.2"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "15c4c2c83f81532e5845a733998b6971faca23490340a418e9b72a3ec9de12ea"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "anstyle-parse"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.1"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "938874ff5980b03a87c5524b3ae5b59cf99b1d6bc836848df7bc5ada9643c333"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"utf8parse",
]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "anstyle-query"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5ca11d4be1bab0c8bc8734a9aa7bf4ee8316d462a08c6ac5052f888fef5b494b"
dependencies = [
"windows-sys",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "anstyle-wincon"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.1.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "58f54d10c6dfa51283a066ceab3ec1ab78d13fae00aa49243a45e4571fb79dfd"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"anstyle",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "anyhow"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.75"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "a4668cab20f66d8d020e1fbc0ebe47217433c1b6c8f2040faf858554e394ace6"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "atty"
version = "0.2.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
dependencies = [
"hermit-abi 0.1.19",
"libc",
"winapi",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "autocfg"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "backtrace"
version = "0.3.69"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2089b7e3f35b9dd2d0ed921ead4f6d318c27680d4a5bd167b3ee120edb105837"
dependencies = [
"addr2line",
"cc",
"cfg-if",
"libc",
"miniz_oxide",
"object",
"rustc-demangle",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "base64"
version = "0.13.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9e1b586273c5702936fe7b7d6896644d8be71e6314cfe09d3167c95f712589e8"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
[[package]]
name = "base64"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.21.4"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "9ba43ea6f343b788c8764558649e08df62f86c6ef251fdaeb1ffd010a9ae50a2"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "bitflags"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "bitflags"
version = "2.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b4682ae6287fcf752ecaabbfcc7b6f9b72aa33933dc23a554d853aea8eea8635"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "block-buffer"
version = "0.10.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3078c7629b62d3f0439517fa394996acacc5cbc91c5a20d8c658e77abd503a71"
dependencies = [
"generic-array",
]
[[package]]
name = "bstr"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.6.2"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "4c2f7349907b712260e64b0afe2f84692af14a454be26187d9df565c7f69266a"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"memchr",
"regex-automata",
"serde",
]
Add page about buddy_system_allocator.
2023-03-16 20:07:58 +02:00
[[package]]
name = "buddy_system_allocator"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "43f9365b6b0c9e1663ca4ca9440c00eda46bc85a3407070be8b5e0d8d1f29629"
dependencies = [
"spin",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "bumpalo"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "3.13.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "a3e2c3daef883ecc1b5d58c15adae93470a91d425f3532ba1695849656af3fc1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "byteorder"
version = "1.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
[[package]]
name = "bytes"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.5.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "a2bd12c1caf447e69cd4528f47f94d203fd2582878ecb9e9465484c4148a8223"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "cc"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.83"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "f1174fb0b6ec23863f8b971027804a42614e347eafb0a95bf0b12cdae21fc4d0"
dependencies = [
"libc",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
Beginnings of an async chat exercise (#627) * beginnings of an async chat exercise * really basic solution * format
2023-05-16 17:51:01 +02:00
[[package]]
name = "chat-async"
version = "0.1.0"
dependencies = [
"futures-util",
"http",
"tokio",
"tokio-websockets",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "chrono"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.30"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "defd4e7873dbddba6c7c91e199c7fcb946abc4a6a4ac3195400bcfb01b5de877"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"android-tzdata",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"iana-time-zone",
"num-traits",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-targets",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
[[package]]
name = "clap"
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
version = "4.4.4"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
checksum = "b1d7b8d5ec32af0fadc644bf1fd509a688c2103b185644bb1e29d164e0703136"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"clap_builder",
]
[[package]]
name = "clap_builder"
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
version = "4.4.4"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
checksum = "5179bb514e4d7c2051749d8fcefa2ed6d06a9f4e6d69faf3805f5d80b8cf8d56"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"anstream",
"anstyle",
"clap_lex",
"strsim",
"terminal_size",
]
[[package]]
name = "clap_complete"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "4.4.1"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "4110a1e6af615a9e6d0a36f805d5c99099f8bab9b8042f5bc1fa220a4a89e36f"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"clap",
]
[[package]]
name = "clap_lex"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.5.1"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "cd7cc57abe963c6d3b9d8be5b06ba7c8957a930305ca90304f24ef040aa6f961"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
name = "colorchoice"
version = "1.0.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "acbf1af155f9b9ef647e42cdc158db4b64a1b61f743629225fde6f3e0be2a7c7"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "comprehensive-rust"
version = "0.1.0"
dependencies = [
"reqwest",
"scraper",
Add unit tests to Safe FFI exercise (#588)
2023-05-04 12:20:47 +02:00
"tempfile",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"thiserror",
]
[[package]]
name = "convert_case"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6245d59a3e82a7fc217c5828a6692dbc6dfb63a0c8c90495621f7b9d79704a0e"
[[package]]
name = "core-foundation"
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "194a7a9e6de53fa55116934067c844d9d749312f75c6f6d0980e8c252f8c2146"
dependencies = [
"core-foundation-sys",
"libc",
]
[[package]]
name = "core-foundation-sys"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.8.4"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "e496a50fda8aacccc86d7529e2c1e0892dbd0f898a6b5645b5561b89c3210efa"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "cpufeatures"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.9"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "a17b76ff3a4162b0b27f354a0c87015ddad39d35f9c0c36607a3bdd175dde1f1"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"libc",
]
[[package]]
name = "crossbeam-channel"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.5.8"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "a33c2bf77f2df06183c3aa30d1e96c0695a313d4f9c453cc3762a6db39f99200"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"cfg-if",
"crossbeam-utils",
]
[[package]]
name = "crossbeam-utils"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.8.16"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "5a22b2d63d4d1dc0b7f1b6b2747dd0088008a9be28b6ddf0b1e7d335e3037294"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"cfg-if",
]
[[package]]
name = "crypto-common"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1bfb12502f3fc46cca1bb51ac28df9d618d813cdc3d2f25b9fe775a34af26bb3"
dependencies = [
"generic-array",
"typenum",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "cssparser"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.29.6"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "f93d03419cb5950ccfd3daf3ff1c7a36ace64609a1a8746d493df1ca0afde0fa"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"cssparser-macros",
"dtoa-short",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"itoa",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"matches",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"phf 0.10.1",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"proc-macro2",
"quote",
"smallvec",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"syn 1.0.109",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "cssparser-macros"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.6.1"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "13b588ba4ac1a99f7f2964d24b3d896ddc6bf847ee3855dbd4366f058cfcd331"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "derive_more"
version = "0.99.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4fb810d30a7c1953f91334de7244731fc3f3c10d7fe163338a35b9f640960321"
dependencies = [
"convert_case",
"proc-macro2",
"quote",
"rustc_version",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"syn 1.0.109",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "digest"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.10.7"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "9ed9a281f7bc9b7576e61468ba615a66a5c8cfdff42420a70aa82701a3b1e292"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"block-buffer",
"crypto-common",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "dtoa"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.9"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "dcbb2bf8e87535c23f7a8a321e364ce21462d0ff10cb6407820e8e96dfff6653"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "dtoa-short"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.4"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "dbaceec3c6e4211c79e7b1800fb9680527106beb2f9c51904a3210c03a448c74"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"dtoa",
]
[[package]]
name = "ego-tree"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3a68a4904193147e0a8dec3314640e6db742afd5f6e634f428a6af230d9b3591"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "elasticlunr-rs"
version = "3.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "41e83863a500656dfa214fee6682de9c5b9f03de6860fec531235ed2ae9f6571"
dependencies = [
"regex",
"serde",
"serde_derive",
"serde_json",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "encoding_rs"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.8.33"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "7268b386296a025e474d5140678f75d6de9493ae55a5d709eeb9dd08149945e1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"cfg-if",
]
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "env_logger"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44533bbbb3bb3c1fa17d9f2e4e38bbbaf8396ba82193c4cb1b6445d711445d36"
dependencies = [
"atty",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"humantime 1.3.0",
"log",
"regex",
"termcolor",
]
[[package]]
name = "env_logger"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "85cdab6a89accf66733ad5a1693a4dcced6aeff64602b634530dd73c1f3ee9f0"
dependencies = [
"humantime 2.1.0",
"is-terminal",
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
"log",
"regex",
"termcolor",
]
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
[[package]]
name = "errno"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.3"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "136526188508e25c6fef639d7927dfb3e0e3084488bf202267829cf7fc23dbdd"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
dependencies = [
"errno-dragonfly",
"libc",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
]
[[package]]
name = "errno-dragonfly"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aa68f1b12764fab894d2755d2518754e71b4fd80ecfb822714a1206c2aab39bf"
dependencies = [
"cc",
"libc",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "fastrand"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.0.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "6999dc1837253364c2ebb0704ba97994bd874e8f195d665c50b7548f6ea92764"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "filetime"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.22"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "d4029edd3e734da6fe05b6cd7bd2960760a616bd2ddd0d59a0124746d6272af0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"cfg-if",
"libc",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"redox_syscall",
"windows-sys",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "fnv"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
[[package]]
name = "foreign-types"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
dependencies = [
"foreign-types-shared",
]
[[package]]
name = "foreign-types-shared"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
[[package]]
name = "form_urlencoded"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.2.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "a62bc1cf6f830c2ec14a513a9fb124d0a213a629668a4186f329db21fe045652"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"percent-encoding",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "fsevent-sys"
version = "4.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "76ee7a02da4d231650c7cea31349b889be2f45ddb3ef3032d2ec8185f6313fd2"
dependencies = [
"libc",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "futf"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "df420e2e84819663797d1ec6544b13c5be84629e7bb00dc960d6917db2987843"
dependencies = [
"mac",
"new_debug_unreachable",
]
[[package]]
name = "futures-channel"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.3.28"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "955518d47e09b25bbebc7a18df10b81f0c766eaf4c4f1cccef2fca5f2a4fb5f2"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"futures-core",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"futures-sink",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "futures-core"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.3.28"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "4bca583b7e26f571124fe5b7561d49cb2868d79116cfa0eefce955557c6fee8c"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "futures-io"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.3.28"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "4fff74096e71ed47f8e023204cfd0aa1289cd54ae5430a9523be060cdb849964"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "futures-macro"
version = "0.3.28"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "89ca545a94061b6365f2c7355b4b32bd20df3ff95f02da9329b34ccc3bd6ee72"
dependencies = [
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "futures-sink"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.3.28"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "f43be4fe21a13b9781a69afa4985b0f6ee0e1afab2c6f454a8cf30e2b2237b6e"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "futures-task"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.3.28"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "76d3d132be6c0e6aa1534069c705a74a5997a356c0dc2f86a47765e5617c5b65"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "futures-util"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.3.28"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "26b01e40b772d54cf6c6d721c1d1abd0647a0106a12ecaa1c186273392a69533"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"futures-core",
"futures-io",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"futures-macro",
"futures-sink",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"futures-task",
"memchr",
"pin-project-lite",
"pin-utils",
"slab",
]
[[package]]
name = "fxhash"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c31b6d751ae2c7f11320402d34e41349dd1016f8d5d45e48c4312bc8625af50c"
dependencies = [
"byteorder",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "generic-array"
version = "0.14.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "85649ca51fd72272d7821adaf274ad91c288277713d9c18820d8499a7ff69e9a"
dependencies = [
"typenum",
"version_check",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "getopts"
version = "0.2.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14dbbfd5c71d70241ecf9e6f13737f7b5ce823821063188d7e46c41d371eebd5"
dependencies = [
"unicode-width",
]
[[package]]
name = "getrandom"
version = "0.1.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8fc3cb4d91f53b50155bdcfd23f6a4c39ae1969c2ae85982b135750cccaf5fce"
dependencies = [
"cfg-if",
"libc",
"wasi 0.9.0+wasi-snapshot-preview1",
]
[[package]]
name = "getrandom"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.10"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "be4136b2a15dd319360be1c07d9933517ccf0be8f16bf62a3bee4f0d618df427"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"cfg-if",
"libc",
"wasi 0.11.0+wasi-snapshot-preview1",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
name = "gimli"
version = "0.28.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "6fb8d784f27acf97159b40fc4db5ecd8aa23b9ad5ef69cdd136d3bc80665f0c0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
name = "globset"
version = "0.4.13"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "759c97c1e17c55525b57192c06a267cda0ac5210b222d6b82189a2338fa1c13d"
dependencies = [
"aho-corasick",
"bstr",
"fnv",
"log",
"regex",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "h2"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.21"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "91fc23aa11be92976ef4729127f1a74adf36d8436f7816b185d18df956790833"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"bytes",
"fnv",
"futures-core",
"futures-sink",
"futures-util",
"http",
"indexmap",
"slab",
"tokio",
"tokio-util",
"tracing",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "handlebars"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "4.4.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "c39b3bc2a8f715298032cf5087e58573809374b08160aa7d750582bdb82d2683"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"log",
"pest",
"pest_derive",
"serde",
"serde_json",
"thiserror",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "hashbrown"
version = "0.12.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8a9ee70c43aaf417c914396645a0fa852624801b24ebb7ae78fe8272889ac888"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "headers"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.9"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "06683b93020a07e3dbcf5f8c0f6d40080d725bea7936fc01ad345c01b97dc270"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"base64 0.21.4",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"bytes",
"headers-core",
"http",
"httpdate",
"mime",
"sha1",
]
[[package]]
name = "headers-core"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e7f66481bfee273957b1f20485a4ff3362987f85b2c236580d81b4eb7a326429"
dependencies = [
"http",
]
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "hermit-abi"
version = "0.1.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "62b467343b94ba476dcb2500d242dadbb39557df889310ac77c5d99100aaac33"
dependencies = [
"libc",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "hermit-abi"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.2"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "443144c8cdadd93ebf52ddb4056d257f5b52c04d3c804e657d19eb73fc33668b"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "html5ever"
version = "0.26.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bea68cab48b8459f17cf1c944c67ddc572d272d9f2b274140f223ecb1da4a3b7"
dependencies = [
"log",
"mac",
"markup5ever",
"proc-macro2",
"quote",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"syn 1.0.109",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "http"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.2.9"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "bd6effc99afb63425aff9b05836f029929e345a6148a14b7ecd5ab67af944482"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"bytes",
"fnv",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"itoa",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "http-body"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d5f38f16d184e36f2408a55281cd658ecbd3ca05cce6d6510a176eca393e26d1"
dependencies = [
"bytes",
"http",
"pin-project-lite",
]
[[package]]
name = "httparse"
version = "1.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d897f394bad6a705d5f4104762e116a75639e470d80901eed05a860a95cb1904"
[[package]]
name = "httpdate"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.3"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "df3b46402a9d5adb4c86a0cf463f42e19994e3ee891101b1841f30a545cb49a9"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "humantime"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "df004cfca50ef23c36850aaaa59ad52cc70d0e90243c3c7737a4dd32dc7a3c4f"
dependencies = [
"quick-error",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "humantime"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a3a5bfb195931eeb336b2a7b4d761daec841b97f947d34394601737a7bba5e4"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "hyper"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.14.27"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "ffb1cfd654a8219eaef89881fdb3bb3b1cdc5fa75ded05d6933b2b382e395468"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"bytes",
"futures-channel",
"futures-core",
"futures-util",
"h2",
"http",
"http-body",
"httparse",
"httpdate",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"itoa",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"pin-project-lite",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"socket2 0.4.9",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"tokio",
"tower-service",
"tracing",
"want",
]
[[package]]
name = "hyper-tls"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d6183ddfa99b85da61a140bea0efc93fdf56ceaa041b37d553518030827f9905"
dependencies = [
"bytes",
"hyper",
"native-tls",
"tokio",
"tokio-native-tls",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "iana-time-zone"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.1.57"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "2fad5b825842d2b38bd206f3e81d6957625fd7f0a361e345c30e01a0ae2dd613"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"android_system_properties",
"core-foundation-sys",
"iana-time-zone-haiku",
"js-sys",
"wasm-bindgen",
"windows",
]
[[package]]
name = "iana-time-zone-haiku"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.1.2"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "f31827a206f56af32e590ba56d5d2d085f558508192593743f16b2306495269f"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"cc",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "idna"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "7d20d6b07bfbc108882d88ed8e37d39636dcc260e15e30c45e6ba089610b917c"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"unicode-bidi",
"unicode-normalization",
]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "ignore"
version = "0.4.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dbe7873dab538a9a44ad79ede1faf5f30d49f9a5c883ddbab48bce81b64b7492"
dependencies = [
"globset",
"lazy_static",
"log",
"memchr",
"regex",
"same-file",
"thread_local",
"walkdir",
"winapi-util",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "indexmap"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "1.9.3"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "bd070e393353796e801d209ad339e89596eb4c8d430d18ede6a1cced8fafbd99"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"autocfg",
"hashbrown",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "inotify"
version = "0.9.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f8069d3ec154eb856955c1c0fbffefbf5f3c40a104ec912d4797314c1801abff"
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"bitflags 1.3.2",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"inotify-sys",
"libc",
]
[[package]]
name = "inotify-sys"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e05c02b5e89bff3b946cedeca278abc628fe811e604f027c45a8aa3cf793d0eb"
dependencies = [
"libc",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "ipnet"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.8.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "28b29a3cd74f0f4598934efe3aeba42bae0eb4680554128851ebbecb02af14e6"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "is-terminal"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.9"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "cb0889898416213fab133e1d33a0e5858a48177452750691bde3666d0fdbaf8b"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"hermit-abi 0.3.2",
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
"rustix",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "itoa"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.9"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "af150ab688ff2122fcef229be89cb50dd66af9e01a4ff320cc137eecc9bacc38"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "js-sys"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.64"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "c5f195fe497f702db0f318b07fdd68edb16955aed830df8363d837542f8f935a"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"wasm-bindgen",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "kqueue"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.8"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "7447f1ca1b7b563588a205fe93dea8df60fd981423a768bc1c0ded35ed147d0c"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"kqueue-sys",
"libc",
]
[[package]]
name = "kqueue-sys"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.4"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "ed9625ffda8729b85e45cf04090035ac368927b8cebc34898e7c120f52e4838b"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"bitflags 1.3.2",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"libc",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "lazy_static"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
[[package]]
name = "libc"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.147"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "b4668fb0ea861c1df094127ac5f1da3409a82116a4ba74fca2e58ef927159bb3"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
[[package]]
name = "linux-raw-sys"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.7"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "1a9bad9f94746442c783ca431b22403b519cd7fbeed0533fdd6328b2f2212128"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "lock_api"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.10"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "c1cc9717a20b1bb222f333e6a92fd32f7d8a18ddc5a3191a11af45dcbf4dcd16"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"autocfg",
"scopeguard",
]
[[package]]
name = "log"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.20"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "b5e6163cb8c49088c2c36f57875e58ccd8c87c7427f7fbd50ea6710b2f3f2e8f"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "mac"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c41e0c4fef86961ac6d6f8a82609f55f31b05e4fce149ac5710e439df7619ba4"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "maplit"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3e2e65a1a2e43cfcb47a895c4c8b10d1f4a61097f9f254f183aee60cad9c651d"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "markup5ever"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a2629bb1404f3d34c2e921f21fd34ba00b206124c81f65c50b43b6aaefeb016"
dependencies = [
"log",
"phf 0.10.1",
"phf_codegen 0.10.0",
"string_cache",
"string_cache_codegen",
"tendril",
]
[[package]]
name = "matches"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
version = "0.1.10"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
checksum = "2532096657941c2fea9c289d370a250971c689d4f143798ff67113ec042024a5"
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
[[package]]
name = "matter"
version = "0.1.0-alpha4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fc16e839c57e0ad77957c42d39baab3692a1c6fa47692066470cddc24a5b0cd0"
dependencies = [
"lazy_static",
"regex",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "mdbook"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.34"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "c55eb7c4dad20cc5bc15181c2aaf43d5689d5c3e0b80b50cc4cf0b7fe72a26d9"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"ammonia",
"anyhow",
"chrono",
"clap",
"clap_complete",
"elasticlunr-rs",
"env_logger 0.10.0",
"futures-util",
"handlebars",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"ignore",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"log",
"memchr",
"notify",
"notify-debouncer-mini",
"once_cell",
"opener",
"pulldown-cmark",
"regex",
"serde",
"serde_json",
"shlex",
"tempfile",
"tokio",
"toml",
"topological-sort",
"warp",
]
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
[[package]]
name = "mdbook-course"
version = "0.1.0"
dependencies = [
"anyhow",
"clap",
"log",
"matter",
"mdbook",
"pretty_env_logger",
"serde_json",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "mdbook-exerciser"
version = "0.1.0"
dependencies = [
"anyhow",
"log",
"mdbook",
"pretty_env_logger",
"pulldown-cmark",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "memchr"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.6.3"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "8f232d6ef707e1956a43342693d2a31e72989554d58299d7a88738cc95b0d35c"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "mime"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.3.17"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "6877bb514081ee2a7ff5ef9de3281f14a4dd4bceac4c09388074a6b5df8a139a"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "mime_guess"
version = "2.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4192263c238a5f0d0c6bfd21f336a313a4ce1c450542449ca191bb657b4642ef"
dependencies = [
"mime",
"unicase",
]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "miniz_oxide"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e7810e0be55b428ada41041c41f32c9f1a42817901b4ccf45fa3d4b6561e74c7"
dependencies = [
"adler",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "mio"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.8.8"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "927a765cd3fc26206e66b296465fa9d3e5ab003e651c1b3c060e7956d96b19d2"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"libc",
"log",
"wasi 0.11.0+wasi-snapshot-preview1",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "native-tls"
version = "0.2.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "07226173c32f2926027b63cce4bcd8076c3552846cbe7925f3aaffeac0a3b92e"
dependencies = [
"lazy_static",
"libc",
"log",
"openssl",
"openssl-probe",
"openssl-sys",
"schannel",
"security-framework",
"security-framework-sys",
"tempfile",
]
[[package]]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
name = "new_debug_unreachable"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e4a24736216ec316047a1fc4252e27dabb04218aa4a3f37c6e7ddbf1f9782b54"
[[package]]
name = "nodrop"
version = "0.1.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "72ef4a56884ca558e5ddb05a1d1e7e1bfd9a68d9ed024c21704cc98872dae1bb"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "normpath"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ec60c60a693226186f5d6edf073232bfb6464ed97eb22cf3b01c1e8198fd97f5"
dependencies = [
"windows-sys",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "notify"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "6.1.1"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "6205bd8bb1e454ad2e27422015fb5e4f2bcc7e08fa8f27058670d208324a4d2d"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"bitflags 2.4.0",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"crossbeam-channel",
"filetime",
"fsevent-sys",
"inotify",
"kqueue",
"libc",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"log",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"mio",
"walkdir",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
[[package]]
name = "notify-debouncer-mini"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "e55ee272914f4563a2f8b8553eb6811f3c0caea81c756346bad15b7e3ef969f0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"crossbeam-channel",
"notify",
]
[[package]]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
name = "num-traits"
version = "0.2.16"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "f30b0abd723be7e2ffca1272140fac1a2f084c77ec3e123c192b66af1ee9e6c2"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"autocfg",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
name = "num_cpus"
version = "1.16.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "4161fcb6d602d4d2081af7c3a45852d875a03dd337a6bfdd6e06407b61342a43"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"hermit-abi 0.3.2",
"libc",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
name = "object"
version = "0.32.1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "9cf5f9dd3933bd50a9e1f149ec995f39ae2c496d31fd772c1fd45ebc27e902b0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"memchr",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "once_cell"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.18.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "dd8b5dd2ae5ed71462c540258bedcb51965123ad7e7ccf4b9a8cafaa4a63576d"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "opener"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.6.1"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "6c62dcb6174f9cb326eac248f07e955d5d559c272730b6c03e396b443b562788"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"bstr",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"normpath",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"winapi",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "openssl"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.10.57"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "bac25ee399abb46215765b1cb35bc0212377e58a061560d8b29b024fd0430e7c"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"bitflags 2.4.0",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"cfg-if",
"foreign-types",
"libc",
"once_cell",
"openssl-macros",
"openssl-sys",
]
[[package]]
name = "openssl-macros"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.1.1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "a948666b637a0f465e8564c73e89d4dde00d72d4d473cc972f390fc3dcee7d9c"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "openssl-probe"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ff011a302c396a5197692431fc1948019154afc178baf7d8e37367442a4601cf"
[[package]]
name = "openssl-sys"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.9.93"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "db4d56a4c0478783083cfafcc42493dd4a981d41669da64b4572a2a089b51b1d"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"cc",
"libc",
"pkg-config",
"vcpkg",
]
[[package]]
name = "parking_lot"
version = "0.12.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3742b2c103b9f06bc9fff0a37ff4912935851bee6d36f3c02bcc755bcfec228f"
dependencies = [
"lock_api",
"parking_lot_core",
]
[[package]]
name = "parking_lot_core"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.9.8"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "93f00c865fe7cabf650081affecd3871070f26767e7b2070a3ffae14c654b447"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"cfg-if",
"libc",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"redox_syscall",
Use mdbook-i18n-helpers crate (#552) The i18n-helpers are now available as a stand-alone crate: https://crates.io/crates/mdbook-i18n-helpers. Because we cache the Rust binaries in our GitHub workflows, I bumped the cache prefix to ensure we use a clean cache. Otherwise, Cargo won’t install the new binaries in mdbook-i18n-helpers because it sees the old ones from this repository.
2023-04-05 16:08:11 +02:00
"smallvec",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-targets",
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
]
[[package]]
Use mdbook-i18n-helpers crate (#552) The i18n-helpers are now available as a stand-alone crate: https://crates.io/crates/mdbook-i18n-helpers. Because we cache the Rust binaries in our GitHub workflows, I bumped the cache prefix to ensure we use a clean cache. Otherwise, Cargo won’t install the new binaries in mdbook-i18n-helpers because it sees the old ones from this repository.
2023-04-05 16:08:11 +02:00
name = "percent-encoding"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.3.0"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "9b2a4787296e9989611394c33f193f676704af1686e70b8f8033ab5ba9a35a94"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "pest"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.7.3"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "d7a4d085fd991ac8d5b05a147b437791b4260b76326baf0fc60cf7c9c27ecd33"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"memchr",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"thiserror",
"ucd-trie",
]
[[package]]
name = "pest_derive"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.7.3"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "a2bee7be22ce7918f641a33f08e3f43388c7656772244e2bbb2477f44cc9021a"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"pest",
"pest_generator",
]
[[package]]
name = "pest_generator"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.7.3"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "d1511785c5e98d79a05e8a6bc34b4ac2168a0e3e92161862030ad84daa223141"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"pest",
"pest_meta",
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
[[package]]
name = "pest_meta"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.7.3"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "b42f0394d3123e33353ca5e1e89092e533d2cc490389f2bd6131c43c634ebc5f"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"once_cell",
"pest",
"sha2",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "phf"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3dfb61232e34fcb633f43d12c58f83c1df82962dcdfa565a4e866ffc17dafe12"
dependencies = [
"phf_shared 0.8.0",
]
[[package]]
name = "phf"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fabbf1ead8a5bcbc20f5f8b939ee3f5b0f6f281b6ad3468b84656b658b455259"
dependencies = [
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"phf_macros",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"phf_shared 0.10.0",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"proc-macro-hack",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "phf_codegen"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cbffee61585b0411840d3ece935cce9cb6321f01c45477d30066498cd5e1a815"
dependencies = [
"phf_generator 0.8.0",
"phf_shared 0.8.0",
]
[[package]]
name = "phf_codegen"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4fb1c3a8bc4dd4e5cfce29b44ffc14bedd2ee294559a294e2a4d4c9e9a6a13cd"
dependencies = [
"phf_generator 0.10.0",
"phf_shared 0.10.0",
]
[[package]]
name = "phf_generator"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "17367f0cc86f2d25802b2c26ee58a7b23faeccf78a396094c13dced0d0182526"
dependencies = [
"phf_shared 0.8.0",
"rand 0.7.3",
]
[[package]]
name = "phf_generator"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5d5285893bb5eb82e6aaf5d59ee909a06a16737a8970984dd7746ba9283498d6"
dependencies = [
"phf_shared 0.10.0",
"rand 0.8.5",
]
[[package]]
name = "phf_macros"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.10.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "58fdf3184dd560f160dd73922bea2d5cd6e8f064bf4b13110abd81b03697b4e0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"phf_generator 0.10.0",
"phf_shared 0.10.0",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"proc-macro-hack",
"proc-macro2",
"quote",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"syn 1.0.109",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "phf_shared"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
checksum = "c00cf8b9eafe68dde5e9eaa2cef8ee84a9336a47d566ec55ca16589633b65af7"
dependencies = [
"siphasher",
]
[[package]]
name = "phf_shared"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6796ad771acdc0123d2a88dc428b5e38ef24456743ddb1744ed628f9815c096"
dependencies = [
"siphasher",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "pin-project"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.1.3"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "fda4ed1c6c173e3fc7a83629421152e01d7b1f9b7f65fb301e490e8cfc656422"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"pin-project-internal",
]
[[package]]
name = "pin-project-internal"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.1.3"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "4359fd9c9171ec6e8c62926d6faaf553a8dc3f64e1507e76da7911b4f6a04405"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "pin-project-lite"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.13"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "8afb450f006bf6385ca15ef45d71d2288452bc3683ce2e2cacc0d18e4be60b58"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
[[package]]
name = "pkg-config"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.27"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "26072860ba924cbfa98ea39c8c19b4dd6a4a25423dbdf219c1eca91aa0cf6964"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "ppv-lite86"
version = "0.2.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5b40af805b3121feab8a3c29f04d8ad262fa8e0561883e7653e024ae4479e6de"
[[package]]
name = "precomputed-hash"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "925383efa346730478fb4838dbe9137d2a47675ad789c546d150a6e1dd4ab31c"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "pretty_env_logger"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "926d36b9553851b8b0005f1275891b392ee4d2d833852c417ed025477350fb9d"
dependencies = [
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"env_logger 0.7.1",
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
"log",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "proc-macro-hack"
version = "0.5.20+deprecated"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dc375e1527247fe1a97d8b7156678dfe7c1af2fc075c9a4db3690ecd2a148068"
[[package]]
name = "proc-macro2"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.66"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "18fb31db3f9bddb2ea821cde30a9f70117e3f119938b5ee630b7403aa6e2ead9"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"unicode-ident",
]
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "pulldown-cmark"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.9.3"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "77a1a2f1f0a7ecff9c31abbe177637be0e97a0aef46cf8738ece09327985d998"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"bitflags 1.3.2",
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
"memchr",
"unicase",
]
[[package]]
name = "quick-error"
version = "1.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a1d01941d82fa2ab50be1e79e6714289dd7cde78eba4c074bc5a4374f650dfe0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "quote"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.33"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "5267fca4496028628a95160fc423a33e8b2e6af8a5302579e322e4b520293cae"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"proc-macro2",
]
[[package]]
name = "rand"
version = "0.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
dependencies = [
"getrandom 0.1.16",
"libc",
"rand_chacha 0.2.2",
"rand_core 0.5.1",
"rand_hc",
"rand_pcg",
]
[[package]]
name = "rand"
version = "0.8.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "34af8d1a0e25924bc5b7c43c079c942339d8f0a8b57c39049bef581b46327404"
dependencies = [
"libc",
"rand_chacha 0.3.1",
"rand_core 0.6.4",
]
[[package]]
name = "rand_chacha"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f4c8ed856279c9737206bf725bf36935d8666ead7aa69b52be55af369d193402"
dependencies = [
"ppv-lite86",
"rand_core 0.5.1",
]
[[package]]
name = "rand_chacha"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
dependencies = [
"ppv-lite86",
"rand_core 0.6.4",
]
[[package]]
name = "rand_core"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
dependencies = [
"getrandom 0.1.16",
]
[[package]]
name = "rand_core"
version = "0.6.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ec0be4795e2f6a28069bec0b5ff3e2ac9bafc99e6a9a7dc3547996c5c816922c"
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"getrandom 0.2.10",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
dependencies = [
"rand_core 0.5.1",
]
[[package]]
name = "rand_pcg"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "16abd0c1b639e9eb4d7c50c0b8100b0d0f849be2349829c740fe8e6eb4816429"
dependencies = [
"rand_core 0.5.1",
]
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
[[package]]
name = "redox_syscall"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "567664f262709473930a4bf9e51bf2ebf3348f2e748ccc50dea20646858f8f29"
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"bitflags 1.3.2",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
]
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "regex"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.9.5"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "697061221ea1b4a94a624f67d0ae2bfe4e22b8a17b6a192afb11046542cc8c47"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
dependencies = [
"aho-corasick",
"memchr",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"regex-automata",
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
"regex-syntax",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "regex-automata"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.8"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "c2f401f4955220693b56f8ec66ee9c78abffd8d1c4f23dc41a23839eb88f0795"
dependencies = [
"aho-corasick",
"memchr",
"regex-syntax",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "regex-syntax"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.7.5"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "dbb5fb1acd8a1a18b3dd5be62d25485eb770e05afb408a9627d14d451bae12da"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "reqwest"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.11.20"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "3e9ad3fe7488d7e34558a2033d45a0c90b72d97b4f80705666fea71472e2e6a1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"base64 0.21.4",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"bytes",
"encoding_rs",
"futures-core",
"futures-util",
"h2",
"http",
"http-body",
"hyper",
"hyper-tls",
"ipnet",
"js-sys",
"log",
"mime",
"native-tls",
"once_cell",
"percent-encoding",
"pin-project-lite",
"serde",
"serde_json",
"serde_urlencoded",
"tokio",
"tokio-native-tls",
"tower-service",
"url",
"wasm-bindgen",
"wasm-bindgen-futures",
"web-sys",
"winreg",
]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "rustc-demangle"
version = "0.1.23"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d626bb9dae77e28219937af045c257c28bfd3f69333c512553507f5f9798cb76"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "rustc_version"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bfa0f585226d2e68097d4f95d113b15b83a82e819ab25717ec0590d9584ef366"
dependencies = [
"semver",
]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "rustix"
version = "0.38.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d7db8590df6dfcd144d22afd1b83b36c21a18d7cbc1dc4bb5295a8712e9eb662"
dependencies = [
"bitflags 2.4.0",
"errno",
"libc",
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
"linux-raw-sys",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "rustls-pemfile"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.3"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "2d3987094b1d07b653b7dfdc3f70ce9a1da9c51ac18c1b06b662e4f9a0e9f4b2"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"base64 0.21.4",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "ryu"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.15"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "1ad4cc8da4ef723ed60bced201181d83791ad433213d8c24efffda1eec85d741"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "same-file"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
dependencies = [
"winapi-util",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "schannel"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.1.22"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "0c3733bf4cf7ea0880754e19cb5a462007c4a8c1914bff372ccc95b464f1df88"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "scoped-tls"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e1cf6437eb19a8f4a6cc0f7dca544973b0b78843adbfeb3683d1a94a0024a294"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "scopeguard"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.2.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "scraper"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.15.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "4c557a9a03db98b0b298b497f0e16cd35a04a1fa9ee1130a6889c0714e0b73df"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"cssparser",
"ego-tree",
"getopts",
"html5ever",
"matches",
"selectors",
"smallvec",
"tendril",
]
[[package]]
name = "security-framework"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.9.2"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "05b64fb303737d99b81884b2c63433e9ae28abebe5eb5045dcdd175dc2ecf4de"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"bitflags 1.3.2",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"core-foundation",
"core-foundation-sys",
"libc",
"security-framework-sys",
]
[[package]]
name = "security-framework-sys"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.9.1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "e932934257d3b408ed8f30db49d85ea163bfe74961f017f405b025af298f0c7a"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"core-foundation-sys",
"libc",
]
[[package]]
name = "selectors"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.24.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "0c37578180969d00692904465fb7f6b3d50b9a2b952b87c23d0e2e5cb5013416"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"bitflags 1.3.2",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"cssparser",
"derive_more",
"fxhash",
"log",
"phf 0.8.0",
"phf_codegen 0.8.0",
"precomputed-hash",
"servo_arc",
"smallvec",
]
[[package]]
name = "semver"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.18"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "b0293b4b29daaf487284529cc2f5675b8e57c61f70167ba415a463651fd6a918"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "serde"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.188"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "cf9e0fcba69a370eed61bcf2b728575f726b50b55cba78064753d708ddc7549e"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"serde_derive",
]
[[package]]
name = "serde_derive"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.188"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "4eca7ac642d82aa35b60049a6eccb4be6be75e599bd2e9adb5f875a737654af2"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "serde_json"
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
version = "1.0.107"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
checksum = "6b420ce6e3d8bd882e9b243c6eed35dbc9a6110c9769e74b584e0d68d1f20c65"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"itoa",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"ryu",
"serde",
]
[[package]]
name = "serde_urlencoded"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3491c14715ca2294c4d6a88f15e84739788c1d030eed8c110436aafdaa2f3fd"
dependencies = [
"form_urlencoded",
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
"itoa",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"ryu",
"serde",
]
[[package]]
name = "servo_arc"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.2.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "d52aa42f8fdf0fed91e5ce7f23d8138441002fa31dca008acf47e6fd4721f741"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"nodrop",
"stable_deref_trait",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "sha1"
version = "0.10.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f04293dc80c3993519f2d7f6f511707ee7094fe0c6d3406feb330cdb3540eba3"
dependencies = [
"cfg-if",
"cpufeatures",
"digest",
]
Beginnings of an async chat exercise (#627) * beginnings of an async chat exercise * really basic solution * format
2023-05-16 17:51:01 +02:00
[[package]]
name = "sha1_smol"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ae1a47186c03a32177042e55dbc5fd5aee900b8e0069a8d70fba96a9375cd012"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "sha2"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.10.7"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "479fb9d862239e610720565ca91403019f2f00410f1864c5aa7479b950a76ed8"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"cfg-if",
"cpufeatures",
"digest",
]
[[package]]
name = "shlex"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.2.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "a7cee0529a6d40f580e7a5e6c495c8fbfe21b7b52795ed4bb5e62cdf92bc6380"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Add the description of the chat-app exercise (#641) * Adds a description of the async chat exercise * Simplifies the use of Error in chat-async * Links the solution to the async chat exercise * Removes the elevator exercise
2023-05-17 19:22:11 +02:00
[[package]]
name = "signal-hook-registry"
version = "1.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d8229b473baa5980ac72ef434c4415e70c4b5e71b423043adb4ba059f89c99a1"
dependencies = [
"libc",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "siphasher"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.11"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "38b58827f4464d87d377d175e90bf58eb00fd8716ff0a62f80356b5e61555d0d"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "slab"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.9"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "8f92a496fb766b417c996b9c5e57daf2f7ad3b0bebe1ccfca4856390e3d3bb67"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"autocfg",
]
[[package]]
name = "smallvec"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.11.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "62bb4feee49fdd9f707ef802e22365a35de4b7b299de4763d44bfea899442ff9"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "socket2"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.4.9"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "64a4a911eed85daf18834cfaa86a79b7d266ff93ff5ba14005426219480ed662"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"libc",
"winapi",
]
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
[[package]]
name = "socket2"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2538b18701741680e0322a2302176d3253a35388e2e62f172f64f4f16605f877"
dependencies = [
"libc",
"windows-sys",
]
Add page about buddy_system_allocator.
2023-03-16 20:07:58 +02:00
[[package]]
name = "spin"
Bump spin from 0.9.6 to 0.9.8 (#545) Bumps [spin](https://github.com/mvdnes/spin-rs) from 0.9.6 to 0.9.8. - [Release notes](https://github.com/mvdnes/spin-rs/releases) - [Changelog](https://github.com/mvdnes/spin-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/mvdnes/spin-rs/commits) --- updated-dependencies: - dependency-name: spin dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-04 08:54:46 +02:00
version = "0.9.8"
Add page about buddy_system_allocator.
2023-03-16 20:07:58 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump spin from 0.9.6 to 0.9.8 (#545) Bumps [spin](https://github.com/mvdnes/spin-rs) from 0.9.6 to 0.9.8. - [Release notes](https://github.com/mvdnes/spin-rs/releases) - [Changelog](https://github.com/mvdnes/spin-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/mvdnes/spin-rs/commits) --- updated-dependencies: - dependency-name: spin dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-04 08:54:46 +02:00
checksum = "6980e8d7511241f8acf4aebddbb1ff938df5eebe98691418c4468d0b72a96a67"
Add page about buddy_system_allocator.
2023-03-16 20:07:58 +02:00
dependencies = [
"lock_api",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "stable_deref_trait"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a8f112729512f8e442d81f95a8a7ddf2b7c6b8a1a6f509a95864142b30cab2d3"
[[package]]
name = "string_cache"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.8.7"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "f91138e76242f575eb1d3b38b4f1362f10d3a43f47d182a5b359af488a02293b"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"new_debug_unreachable",
"once_cell",
"parking_lot",
"phf_shared 0.10.0",
"precomputed-hash",
"serde",
]
[[package]]
name = "string_cache_codegen"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6bb30289b722be4ff74a408c3cc27edeaad656e06cb1fe8fa9231fa59c728988"
dependencies = [
"phf_generator 0.10.0",
"phf_shared 0.10.0",
"proc-macro2",
"quote",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "strsim"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "syn"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "1.0.109"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "72b64191b275b66ffe2469e8af2c1cfe3bafa67b529ead792a6d0160888b4237"
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
[[package]]
name = "syn"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.0.31"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "718fa2415bcb8d8bd775917a1bf12a7931b6dfa890753378538118181e0cb398"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
[[package]]
name = "tempfile"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "3.8.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "cb94d2f3cc536af71caac6b6fcebf65860b347e7ce0cc9ebe8f70d3e521054ef"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"cfg-if",
"fastrand",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"redox_syscall",
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
"rustix",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "tendril"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d24a120c5fc464a3458240ee02c299ebcb9d67b5249c8848b09d639dca8d7bb0"
dependencies = [
"futf",
"mac",
"utf-8",
]
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "termcolor"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be55cf8942feac5c765c2c993422806843c9a9a45d4d5c407ad6dd2ea95eb9b6"
dependencies = [
"winapi-util",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "terminal_size"
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
version = "0.3.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
checksum = "21bebf2b7c9e0a515f6e0f8c51dc0f8e4696391e6f1ff30379559f8365fb0df7"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Add mdbook-course to handle parsing frontmatter (#1224) In v2 of the course, I'd like to include an estimate of the time to be spent on each segment in the Markdown file. I think a good place for such metadata is in the frontmatter. For review purposes, though, I just want to display that information. So, this is a start at a new mdbook preprocessor that just separates out the frontmatter and includes it in a `<pre>` block. Eventually, I'd like to parse it and put the time in the speaker notes. --------- Co-authored-by: Martin Geisler <martin@geisler.net>
2023-09-20 16:01:53 +02:00
"rustix",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "thiserror"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.48"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "9d6d7a740b8a666a7e828dd00da9c0dc290dff53154ea77ac109281de90589b7"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.48"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "49922ecae66cc8a249b77e68d1d0623c1b2c514f0060c27cdc68bd62a1219d35"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
]
[[package]]
name = "thread_local"
version = "1.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3fdd6f064ccff2d6567adcb3873ca630700f00b5ad3f060c25b5dcfd9a4ce152"
dependencies = [
"cfg-if",
"once_cell",
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "tinyvec"
version = "1.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "87cc5ceb3875bb20c2890005a4e226a4651264a5c75edb2421b52861a0a0cb50"
dependencies = [
"tinyvec_macros",
]
[[package]]
name = "tinyvec_macros"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.1.1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "1f3ccbac311fea05f86f61904b462b55fb3df8837a366dfc601a0161d0532f20"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "tokio"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.32.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "17ed6077ed6cd6c74735e21f37eb16dc3935f96878b1fe961074089cc80893f9"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"backtrace",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"bytes",
"libc",
"mio",
"num_cpus",
Add the description of the chat-app exercise (#641) * Adds a description of the async chat exercise * Simplifies the use of Error in chat-async * Links the solution to the async chat exercise * Removes the elevator exercise
2023-05-17 19:22:11 +02:00
"parking_lot",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"pin-project-lite",
Add the description of the chat-app exercise (#641) * Adds a description of the async chat exercise * Simplifies the use of Error in chat-async * Links the solution to the async chat exercise * Removes the elevator exercise
2023-05-17 19:22:11 +02:00
"signal-hook-registry",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"socket2 0.5.3",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"tokio-macros",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-sys",
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "tokio-macros"
Beginnings of an async chat exercise (#627) * beginnings of an async chat exercise * really basic solution * format
2023-05-16 17:51:01 +02:00
version = "2.1.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Beginnings of an async chat exercise (#627) * beginnings of an async chat exercise * really basic solution * format
2023-05-16 17:51:01 +02:00
checksum = "630bdcf245f78637c13ec01ffae6187cca34625e8c63150d424b59e55af2675e"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "tokio-native-tls"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.3.1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "bbae76ab933c85776efabc971569dd6119c580d8f5d448769dec1764bf796ef2"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"native-tls",
"tokio",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "tokio-stream"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.1.14"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "397c988d37662c7dda6d2208364a706264bf3d6138b11d436cbac0ad38832842"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"futures-core",
"pin-project-lite",
"tokio",
]
[[package]]
name = "tokio-tungstenite"
version = "0.18.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "54319c93411147bced34cb5609a80e0a8e44c5999c93903a81cd866630ec0bfd"
dependencies = [
"futures-util",
"log",
"tokio",
"tungstenite",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "tokio-util"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.7.8"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "806fe8c2c87eccc8b3267cbae29ed3ab2d0bd37fca70ab622e46aaa9375ddb7d"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"bytes",
"futures-core",
"futures-sink",
"pin-project-lite",
"tokio",
"tracing",
]
Beginnings of an async chat exercise (#627) * beginnings of an async chat exercise * really basic solution * format
2023-05-16 17:51:01 +02:00
[[package]]
name = "tokio-websockets"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.0"
Beginnings of an async chat exercise (#627) * beginnings of an async chat exercise * really basic solution * format
2023-05-16 17:51:01 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "6475b54c23ea1ed20e4ef66fe8ae4c66e6ccc714bfef2920c6165827b7904d34"
Beginnings of an async chat exercise (#627) * beginnings of an async chat exercise * really basic solution * format
2023-05-16 17:51:01 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"base64 0.21.4",
Beginnings of an async chat exercise (#627) * beginnings of an async chat exercise * really basic solution * format
2023-05-16 17:51:01 +02:00
"bytes",
"fastrand",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"futures-core",
"futures-sink",
Beginnings of an async chat exercise (#627) * beginnings of an async chat exercise * really basic solution * format
2023-05-16 17:51:01 +02:00
"http",
"httparse",
"sha1_smol",
"tokio",
"tokio-util",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "toml"
version = "0.5.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f4f7f0dd8d50a853a531c426359045b1998f04219d88799810762cd4ad314234"
dependencies = [
"serde",
]
[[package]]
name = "topological-sort"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ea68304e134ecd095ac6c3574494fc62b909f416c4fca77e440530221e549d3d"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "tower-service"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6bc1c9ce2b5135ac7f93c72918fc37feb872bdc6a5533a8b85eb4b86bfdae52"
[[package]]
name = "tracing"
version = "0.1.37"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8ce8c33a8d48bd45d624a6e523445fd21ec13d3653cd51f681abf67418f54eb8"
dependencies = [
"cfg-if",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
"log",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"pin-project-lite",
"tracing-core",
]
[[package]]
name = "tracing-core"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.1.31"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "0955b8137a1df6f1a2e9a37d8a6656291ff0297c1a97c24e0d8425fe2312f79a"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"once_cell",
]
[[package]]
name = "try-lock"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3528ecfd12c466c6f163363caf2d02a71161dd5e1cc6ae7b34207ea2d42d81ed"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "tungstenite"
version = "0.18.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "30ee6ab729cd4cf0fd55218530c4522ed30b7b6081752839b68fcec8d0960788"
dependencies = [
"base64 0.13.1",
"byteorder",
"bytes",
"http",
"httparse",
"log",
"rand 0.8.5",
"sha1",
"thiserror",
"url",
"utf-8",
]
[[package]]
name = "typenum"
version = "1.16.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "497961ef93d974e23eb6f433eb5fe1b7930b659f06d12dec6fc44a8f554c0bba"
[[package]]
name = "ucd-trie"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.1.6"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "ed646292ffc8188ef8ea4d1e0e0150fb15a5c2e12ad9b8fc191ae7a8a7f3c4b9"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "unicase"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.7.0"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "f7d2d4dafb69621809a81864c9c1b864479e1235c0dd4e199924b9742439ed89"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
dependencies = [
"version_check",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "unicode-bidi"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
version = "0.3.13"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
checksum = "92888ba5573ff080736b3648696b70cafad7d250551175acbaa4e0385b3e1460"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "unicode-ident"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "1.0.11"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "301abaae475aa91687eb82514b328ab47a211a533026cb25fc3e519b86adfc3c"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "unicode-normalization"
version = "0.1.22"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c5713f0fc4b5db668a2ac63cdb7bb4469d8c9fed047b1d0292cc7b0ce2ba921"
dependencies = [
"tinyvec",
]
[[package]]
name = "unicode-width"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0edd1e5b14653f783770bce4a4dabb4a5108a5370a5f5d8cfe8710c361f6c8b"
[[package]]
name = "url"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.4.1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "143b538f18257fac9cad154828a57c6bf5157e1aa604d4816b5995bf6de87ae5"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"form_urlencoded",
"idna",
"percent-encoding",
]
[[package]]
name = "utf-8"
version = "0.7.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "09cc8ee72d2a9becf2f2febe0205bbed8fc6615b7cb429ad062dc7b7ddd036a9"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "utf8parse"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "711b9620af191e0cdc7468a8d14e709c3dcdb115b36f838e601583af800a370a"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "vcpkg"
version = "0.2.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "accd4ea62f7bb7a82fe23066fb0957d48ef677f6eeb8215f372f52e48bb32426"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "version_check"
version = "0.9.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "walkdir"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "2.4.0"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "d71d857dc86794ca4c280d616f7da00d2dbfd8cd788846559a6813e6aa4b54ee"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"same-file",
"winapi-util",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "want"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "bfa7760aed19e106de2c7c0b581b509f2f25d3dacaf737cb82ac61bc6d760b0e"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"try-lock",
]
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "warp"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.5"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "ba431ef570df1287f7f8b07e376491ad54f84d26ac473489427231e1718e1f69"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
"bytes",
"futures-channel",
"futures-util",
"headers",
"http",
"hyper",
"log",
"mime",
"mime_guess",
"percent-encoding",
"pin-project",
"rustls-pemfile",
"scoped-tls",
"serde",
"serde_json",
"serde_urlencoded",
"tokio",
"tokio-stream",
"tokio-tungstenite",
"tokio-util",
"tower-service",
"tracing",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "wasi"
version = "0.9.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
[[package]]
name = "wasi"
version = "0.11.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
[[package]]
name = "wasm-bindgen"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.87"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "7706a72ab36d8cb1f80ffbf0e071533974a60d0a308d01a5d0375bf60499a342"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"cfg-if",
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.87"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "5ef2b6d3c510e9625e5fe6f509ab07d66a760f0885d858736483c32ed7809abd"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"bumpalo",
"log",
"once_cell",
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-futures"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.4.37"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "c02dbc21516f9f1f04f187958890d7e6026df8d16540b7ad9492bc34a67cea03"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"cfg-if",
"js-sys",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "wasm-bindgen-macro"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.87"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "dee495e55982a3bd48105a7b947fd2a9b4a8ae3010041b9e0faab3f9cd028f1d"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"quote",
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.87"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "54681b18a46765f095758388f2d0cf16eb8d4169b639ab575a8f5693af210c7b"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.2.87"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "ca6ad05a4870b2bf5fe995117d3728437bd27d7cd5f06f13c17443ef369775a1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "web-sys"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.3.64"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "9b85cbef8c220a6abc02aefd892dfc0fc23afb1c6a426316ec33253a3877249b"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
"js-sys",
"wasm-bindgen",
]
[[package]]
name = "winapi"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
Add utility to build exercise starting directory from Markdown.
2023-03-30 13:42:21 +02:00
[[package]]
name = "winapi-util"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
dependencies = [
"winapi",
]
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add a cargo workspace containing both crates (#321) * Move Cargo.toml for exercises to exercises directory. * Create a workspace with both exercises and i18n-helpers. * Build in CI as well as testing. * Binaries must have a main function. * No need for workspaces configuration for caching anymore.
2023-02-02 18:14:34 +02:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "windows"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e686886bc078bc1b0b600cac0147aadb815089b6e4da64016cbd754b6342700f"
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-targets",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
[[package]]
name = "windows-sys"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "677d2418bec65e3338edb076e806bc1ec15693c5d0104683f2efe857f61056a9"
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows-targets",
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
]
[[package]]
name = "windows-targets"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.48.5"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "9a2fa6e2155d7247be68c096456083145c183cbbbc2764150dda45a87197940c"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"windows_aarch64_gnullvm",
"windows_aarch64_msvc",
"windows_i686_gnu",
"windows_i686_msvc",
"windows_x86_64_gnu",
"windows_x86_64_gnullvm",
"windows_x86_64_msvc",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
[[package]]
name = "windows_aarch64_gnullvm"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.48.5"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "2b38e32f0abccf9987a4e3079dfb67dcd799fb61361e53e2882c3cbaf0d905d8"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "windows_aarch64_msvc"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.48.5"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "dc35310971f3b2dbbf3f0690a219f40e2d9afcf64f9ab7cc1be722937c26b4bc"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "windows_i686_gnu"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.48.5"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "a75915e7def60c94dcef72200b9a8e58e5091744960da64ec734a6c6e9b3743e"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "windows_i686_msvc"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.48.5"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "8f55c233f70c4b27f66c523580f78f1004e8b5a8b659e05a4eb49d4166cca406"
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
[[package]]
name = "windows_x86_64_gnu"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.48.5"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "53d40abd2583d23e4718fddf1ebec84dbff8381c07cae67ff7768bbf19c6718e"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
[[package]]
name = "windows_x86_64_gnullvm"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.48.5"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "0b7b52767868a23d5bab768e390dc5f5c55825b6d30b86c844ff2dc7414044cc"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Update `scraper` dependency (#547) * Update scraper dependency to 0.15.0 No code changes required because of this. * Update dependencies in lock file
2023-04-04 14:27:46 +02:00
[[package]]
name = "windows_x86_64_msvc"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.48.5"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "ed94fce61571a4006852b7389a063ab983c02eb1bb37b47f8272ce92d06d9538"
Make exerciser an mdbook renderer.
2023-04-03 16:01:13 +02:00
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
[[package]]
name = "winreg"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.50.0"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "524e57b2c537c0f9b1e69f1965311ec12182b4122e45035b1508cd24d2adadb1"
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
dependencies = [
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"cfg-if",
"windows-sys",
Add `Cargo.lock` This captures a set of known-good dependencies for the provided solutions.
2023-01-03 15:40:22 +02:00
]
Write page about zerocopy.
2023-03-16 17:32:31 +02:00
[[package]]
name = "zerocopy"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.6.4"
Write page about zerocopy.
2023-03-16 17:32:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "20707b61725734c595e840fb3704378a0cd2b9c74cc9e6e20724838fc6a1e2f9"
Write page about zerocopy.
2023-03-16 17:32:31 +02:00
dependencies = [
"byteorder",
"zerocopy-derive",
]
[[package]]
name = "zerocopy-derive"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
version = "0.6.4"
Write page about zerocopy.
2023-03-16 17:32:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
checksum = "56097d5b91d711293a42be9289403896b68654625021732067eac7a4ca388a1f"
Write page about zerocopy.
2023-03-16 17:32:31 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies in chat-app exercise (#1195) Hello there :wave: I'm the author of the `tokio-websockets` crate and today we published version `0.4.0` of the crate, which finally makes the public API consistent and aligns it with expectations. `WebsocketStream` now implements the `Stream` trait, so calling `next()` has to be done via `StreamExt` now. `connect()` returns a tuple of `(WebsocketStream, Response)`, so that has to be deconstructed now. And finally, `as_text()` now returns an `Option<&str>` instead of `Result<&str, Error>`. And, *very* importantly: The old `WebsocketStream::next` was **not** cancellation safe, the new `Stream` implementation is. The exercise uses `select!`, which very well might have caused misbehavior. Since we also emptied the default features, I've added the very minimal ones required to compile the exercise. This is my first contribution here, so feel free to point me to some things if I'm missing anything. I wasn't really sure what to do about the translations, I guess I should leave them as is and they'll be updated by translators in other PRs? Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2023-09-11 16:19:13 +02:00
"syn 2.0.31",
Write page about zerocopy.
2023-03-16 17:32:31 +02:00
]
[[package]]
name = "zerocopy-example"
version = "0.1.0"
dependencies = [
"zerocopy",
]
Reference in New Issue Copy Permalink