build(deps): bump tokio from 1.17.0 to 1.25.0 in /docker-images/syntax-highlighter

[dependabot]

Bumps tokio from 1.17.0 to 1.25.0.

Release notes

Sourced from tokio's releases.

Tokio v1.25.0

1.25.0 (January 28, 2023)

Fixed

• rt: fix runtime metrics reporting (#5330)

Added

• sync: add broadcast::Sender::len (#5343)

Changed

• fs: increase maximum read buffer size to 2MiB (#5397)

#5330: tokio-rs/tokio#5330 #5343: tokio-rs/tokio#5343 #5397: tokio-rs/tokio#5397

Tokio v1.24.1

This release fixes a compilation failure on targets without AtomicU64 when using rustc older than 1.63. (#5356)

#5356: tokio-rs/tokio#5356

Tokio v1.24.0

The highlight of this release is the reduction of lock contention for all I/O operations (#5300). We have received reports of up to a 20% improvement in CPU utilization and increased throughput for real-world I/O heavy applications.

Fixed

• rt: improve native AtomicU64 support detection (#5284)

Added

• rt: add configuration option for max number of I/O events polled from the OS per tick (#5186)
• rt: add an environment variable for configuring the default number of worker threads per runtime instance (#4250)

Changed

• sync: reduce MPSC channel stack usage (#5294)
• io: reduce lock contention in I/O operations (#5300)
• fs: speed up read_dir() by chunking operations (#5309)
• rt: use internal ThreadId implementation (#5329)
• test: don't auto-advance time when a spawn_blocking task is running (#5115)

#5186: tokio-rs/tokio#5186 #5294: tokio-rs/tokio#5294 #5284: tokio-rs/tokio#5284 #4250: tokio-rs/tokio#4250 #5300: tokio-rs/tokio#5300 #5329: tokio-rs/tokio#5329 #5115: tokio-rs/tokio#5115

... (truncated)

Commits

• 88b1eb5 chore: prepare Tokio v1.25.0 release (#5408)
• 1f50c57 metrics: fix steal_count docs, add steal_operations (#5330)
• a18b364 chore: update year in LICENSE files (#5402)
• fe2dcb9 io: increase MAX_BUF from 16384 to 2MiB (#5397)
• c90757f tests: condition unwinding tests on cfg(panic = "unwind") (#5384)
• f3f8e4f chore: update nix to 0.26 (#5385)
• 42bec96 Merge branch 'tokio-1.24.x' into master
• 4f6a95b chore: prepare Tokio v1.24.2 release
• 3d33610 Merge branch 'tokio-1.20.x' into tokio-1.24.x
• 38a9c6c Merge branch 'tokio-1.20.x' into master
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

_{Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.}

[pull-request-quantifier-deprecated]

This PR has 81 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Small
Size       : +56 -25
Percentile : 32.4%

Total files changed: 1

Change summary by file extension:
.lock : +56 -25

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.