Search
680 results for “hds”
-
I have the first song from #Enredados - #Tangled in Spanish (Castillian version) - stuck in my head and have had for 3 days.
-
I have the first song from #Enredados - #Tangled in Spanish (Castillian version) - stuck in my head and have had for 3 days.
-
I have the first song from #Enredados - #Tangled in Spanish (Castillian version) - stuck in my head and have had for 3 days.
-
add flags and configurations for warnings
https://github.com/tokio-rs/console/pull/493add --allow flag
https://github.com/tokio-rs/console/pull/513These two features allow you to choose which lints you want running in tokio-console.
Don't want a warning for tasks that have never yielded? It's as easy as:
tokio-console --allow never-yielded
They can all be allowed (no warnings) with:
tokio-console --allow all
-
add flags and configurations for warnings
https://github.com/tokio-rs/console/pull/493add --allow flag
https://github.com/tokio-rs/console/pull/513These two features allow you to choose which lints you want running in tokio-console.
Don't want a warning for tasks that have never yielded? It's as easy as:
tokio-console --allow never-yielded
They can all be allowed (no warnings) with:
tokio-console --allow all
-
add flags and configurations for warnings
https://github.com/tokio-rs/console/pull/493add --allow flag
https://github.com/tokio-rs/console/pull/513These two features allow you to choose which lints you want running in tokio-console.
Don't want a warning for tasks that have never yielded? It's as easy as:
tokio-console --allow never-yielded
They can all be allowed (no warnings) with:
tokio-console --allow all
-
add flags and configurations for warnings
https://github.com/tokio-rs/console/pull/493add --allow flag
https://github.com/tokio-rs/console/pull/513These two features allow you to choose which lints you want running in tokio-console.
Don't want a warning for tasks that have never yielded? It's as easy as:
tokio-console --allow never-yielded
They can all be allowed (no warnings) with:
tokio-console --allow all
-
add flags and configurations for warnings
https://github.com/tokio-rs/console/pull/493add --allow flag
https://github.com/tokio-rs/console/pull/513These two features allow you to choose which lints you want running in tokio-console.
Don't want a warning for tasks that have never yielded? It's as easy as:
tokio-console --allow never-yielded
They can all be allowed (no warnings) with:
tokio-console --allow all
-
lints trigger with non-async tasks
https://github.com/tokio-rs/console/pull/517The lints available in Tokio-console are only really applicable to async and local tasks. Not to the other kinds (blocking, block_on).
Yet the lints were getting triggered on those tasks as well, which were all false positives.
This release includes a fix for that!
-
lints trigger with non-async tasks
https://github.com/tokio-rs/console/pull/517The lints available in Tokio-console are only really applicable to async and local tasks. Not to the other kinds (blocking, block_on).
Yet the lints were getting triggered on those tasks as well, which were all false positives.
This release includes a fix for that!
-
lints trigger with non-async tasks
https://github.com/tokio-rs/console/pull/517The lints available in Tokio-console are only really applicable to async and local tasks. Not to the other kinds (blocking, block_on).
Yet the lints were getting triggered on those tasks as well, which were all false positives.
This release includes a fix for that!
-
lints trigger with non-async tasks
https://github.com/tokio-rs/console/pull/517The lints available in Tokio-console are only really applicable to async and local tasks. Not to the other kinds (blocking, block_on).
Yet the lints were getting triggered on those tasks as well, which were all false positives.
This release includes a fix for that!
-
lints trigger with non-async tasks
https://github.com/tokio-rs/console/pull/517The lints available in Tokio-console are only really applicable to async and local tasks. Not to the other kinds (blocking, block_on).
Yet the lints were getting triggered on those tasks as well, which were all false positives.
This release includes a fix for that!
-
replace target column with kind column in tasks view
https://github.com/tokio-rs/console/pull/478The task kind is more useful (and shorter) than the target, so the kind has been given its own column and target has been relegated to the catch all "Fields" column.
This work also enabled the next fix...
-
replace target column with kind column in tasks view
https://github.com/tokio-rs/console/pull/478The task kind is more useful (and shorter) than the target, so the kind has been given its own column and target has been relegated to the catch all "Fields" column.
This work also enabled the next fix...
-
replace target column with kind column in tasks view
https://github.com/tokio-rs/console/pull/478The task kind is more useful (and shorter) than the target, so the kind has been given its own column and target has been relegated to the catch all "Fields" column.
This work also enabled the next fix...
-
replace target column with kind column in tasks view
https://github.com/tokio-rs/console/pull/478The task kind is more useful (and shorter) than the target, so the kind has been given its own column and target has been relegated to the catch all "Fields" column.
This work also enabled the next fix...
-
replace target column with kind column in tasks view
https://github.com/tokio-rs/console/pull/478The task kind is more useful (and shorter) than the target, so the kind has been given its own column and target has been relegated to the catch all "Fields" column.
This work also enabled the next fix...
-
Don't save poll_ops if no-one is receiving them
https://github.com/tokio-rs/console/pull/501Poll ops were previously not being removed from the console-subscriber local state after the retention period. This is a not-very-nice memory leak.
Since tokio-console doesn't show completed poll ops anyway, they won't be stored in the console-subscriber local state if no client is attached. This will reduce the subscriber memory footprint in that case (no client connected).
-
Don't save poll_ops if no-one is receiving them
https://github.com/tokio-rs/console/pull/501Poll ops were previously not being removed from the console-subscriber local state after the retention period. This is a not-very-nice memory leak.
Since tokio-console doesn't show completed poll ops anyway, they won't be stored in the console-subscriber local state if no client is attached. This will reduce the subscriber memory footprint in that case (no client connected).
-
Don't save poll_ops if no-one is receiving them
https://github.com/tokio-rs/console/pull/501Poll ops were previously not being removed from the console-subscriber local state after the retention period. This is a not-very-nice memory leak.
Since tokio-console doesn't show completed poll ops anyway, they won't be stored in the console-subscriber local state if no client is attached. This will reduce the subscriber memory footprint in that case (no client connected).
-
Don't save poll_ops if no-one is receiving them
https://github.com/tokio-rs/console/pull/501Poll ops were previously not being removed from the console-subscriber local state after the retention period. This is a not-very-nice memory leak.
Since tokio-console doesn't show completed poll ops anyway, they won't be stored in the console-subscriber local state if no client is attached. This will reduce the subscriber memory footprint in that case (no client connected).
-
Don't save poll_ops if no-one is receiving them
https://github.com/tokio-rs/console/pull/501Poll ops were previously not being removed from the console-subscriber local state after the retention period. This is a not-very-nice memory leak.
Since tokio-console doesn't show completed poll ops anyway, they won't be stored in the console-subscriber local state if no client is attached. This will reduce the subscriber memory footprint in that case (no client connected).
-
There is also a minimal gRPC-web client in the console-subscriber examples directory:
https://github.com/tokio-rs/console/pull/526 -
There is also a minimal gRPC-web client in the console-subscriber examples directory:
https://github.com/tokio-rs/console/pull/526 -
There is also a minimal gRPC-web client in the console-subscriber examples directory:
https://github.com/tokio-rs/console/pull/526 -
There is also a minimal gRPC-web client in the console-subscriber examples directory:
https://github.com/tokio-rs/console/pull/526 -
There is also a minimal gRPC-web client in the console-subscriber examples directory:
https://github.com/tokio-rs/console/pull/526 -
Support for gRPC web!
https://github.com/tokio-rs/console/pull/498You can now run Tokio Console with a gRPC-web interface. This would allow you to use a client connecting from a web browser.
Of course, tokio-console is a command line tool, it doesn't run in a web browser, so why would you want this?
Because Tokio Console contributor Rustin has built a web version of the console as well!
Check it out:
https://github.com/hi-rustin/tokio-console-web -
Support for gRPC web!
https://github.com/tokio-rs/console/pull/498You can now run Tokio Console with a gRPC-web interface. This would allow you to use a client connecting from a web browser.
Of course, tokio-console is a command line tool, it doesn't run in a web browser, so why would you want this?
Because Tokio Console contributor Rustin has built a web version of the console as well!
Check it out:
https://github.com/hi-rustin/tokio-console-web