Update docs based on code PR #5878

[runllm-pr-agent]

Changes Made

• CHANGELOG/CHANGELOG-v1.3.0-b6.md
  • Pull in [Doc hub](https://github.co... --> Pull in [Doc hub](https://github.co...: The changelog should reflect the new sections added to the documentation about Input Caching and Output Caching, as well as the updates made to the explanations of caching parameters. This ensures that users are aware of the improvements and simplifications made to the caching documentation.
• docs/user_guide/development_lifecycle/caching.md
  • There are four parameters and one c... --> There are four parameters and one c...: The code changes introduce new sections on input and output caching, which are not currently present in the documentation. These sections provide a comprehensive overview of caching mechanisms, aligning with the goal of simplifying the documentation for better user understanding.
  • The flytekit package uses the [disk... --> Flyte uses a tool called [diskcache...: The code changes update the explanation of how Flyte uses the diskcache package for local caching. The revised explanation is clearer and more concise, which aligns with the goal of simplifying the documentation for better user understanding.
• docs/user_guide/development_lifecycle/caching.md
  • Flyte provides the ability to cache... --> Flyte provides the ability to cache...: The code changes introduce the concept of input caching in addition to output caching, so the documentation should reflect that both input and output caching are supported.
  • Let's watch a brief explanation of ... --> ### Input CachingIn Flyte, input ca...: The code changes add new sections on input and output caching, which should be included in the documentation to provide a comprehensive overview of caching mechanisms in Flyte.
  • *** cache_version (str): Part of the ... --> * cache_version (str): Part of ...**: The code changes clarify the purpose of the cache_version parameter, so the documentation should be updated to include this clarification for better user understanding.
  • *** cache_ignore_input_vars (Tuple[st... --> * cache_ignore_input_vars (Tuple...**: The code changes provide a clearer explanation of the cache_ignore_input_vars` parameter, so the documentation should be updated to reflect this improved explanation.
  • The flytekit package uses the [disk... --> Flyte uses a tool called [diskcache...: The code changes update the description of how Flyte uses diskcache for memoization, so the documentation should be updated to reflect this new description.
• docs/user_guide/development_lifecycle/caching.md
  • are stored under ~/.flyte/local-cac... --> Flyte uses a tool called [diskcache...: The documentation needs to be updated to reflect the new explanation of how Flyte uses diskcache for memoization, as introduced in the code changes.
• docs/user_guide/development_lifecycle/cache_serializing.md
  • Serializing means only executing a ... --> Serializing means only executing a ...: The code changes added a section on output caching, emphasizing its value for tasks with expensive or time-consuming operations. This addition should be reflected in the cache serializing documentation to highlight its relevance.
  • Task cache serializing is disabled ... --> Task cache serializing is disabled ...: The code changes introduced input caching, which is relevant to scenarios where tasks are re-executed. This should be mentioned in the cache serializing documentation to provide a comprehensive understanding of caching benefits.
• docs/user_guide/development_lifecycle/cache_serializing.md
  • There are four parameters and one c... --> ### Input CachingIn Flyte, input ca...: The new sections on input and output caching provide a comprehensive overview of caching mechanisms in Flyte, which enhances user understanding. These sections should be added to the documentation to reflect the code changes.
  • Flyte handles task execution failur... --> Flyte handles task execution failur...: The explanation of how Flyte uses diskcache for local caching is relevant to the section discussing task execution and caching. This addition provides clarity on the caching mechanism used by Flyte, aligning with the code changes.
• rfc/system/2633-eviction-of-cached-task-outputs.md
  • ## 4 Metrics & DashboardsAs the imp... --> ## 4 Metrics & DashboardsAs the imp...: The original text contains a grammatical error in the phrase 'The proposed cache eviction changes introduces'. The verb 'introduces' should be 'introduce' to agree with the plural subject 'changes'. This correction improves the grammatical accuracy of the documentation.
• CHANGELOG/CHANGELOG-v0.17.0.md
  • Tasks that have cache=True should n... --> Tasks that have cache=True should...: The documentation should be updated to reflect the new sections on input and output caching added to the caching documentation. This ensures users are aware of the comprehensive overview provided in the updated documentation.

[welcome]

Thank you for opening this pull request! 🙌

These tips will help get your PR across the finish line:

• Most of the repos have a PR template; if not, fill it out to the best of your knowledge.
• Sign off your commits (Reference: DCO Guide).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.81%. Comparing base (7e78e71) to head (8108ddf).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5898   +/-   ##
=======================================
  Coverage   36.81%   36.81%           
=======================================
  Files        1309     1309           
  Lines      130895   130895           
=======================================
  Hits        48185    48185           
  Misses      78528    78528           
  Partials     4182     4182           

Flag	Coverage Δ
unittests-datacatalog	51.58% <ø> (ø)
unittests-flyteadmin	54.03% <ø> (ø)
unittests-flytecopilot	11.73% <ø> (ø)
unittests-flytectl	62.40% <ø> (ø)
unittests-flyteidl	6.92% <ø> (ø)
unittests-flyteplugins	53.59% <ø> (ø)
unittests-flytepropeller	43.00% <ø> (ø)
unittests-flytestdlib	55.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.