Sweep: Update all occurrences of file_cache to use sha1 instead of md5. There are two files.

[sweep-nightly]

Description

This pull request updates the hashing algorithm used in our file caching mechanism from md5 to sha1 across various files and documentation. The change is made to enhance the security and reliability of our hashing process for object serialization and caching.

Summary

• Changed hashing algorithm from md5 to sha1 to improve security.
• Updated the recursive_hash function in docs/pages/blogs/file-cache.mdx, docs/public/file_cache.py, and sweepai/logn/cache.py to use sha1.
• Modified the error message in the documentation to reflect the use of sha1 instead of md5.
• Ensured consistency in hashing across documentation and source code files.

Fixes #3333.

---

🎉 Latest improvements to Sweep:

• New dashboard launched for real-time tracking of Sweep issues, covering all stages from search to coding.
• Integration of OpenAI's latest Assistant API for more efficient and reliable code planning and editing, improving speed by 3x.
• Use the GitHub issues extension for creating Sweep issues directly from your editor.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-nightly]

Rollback Files For Sweep

• Rollback changes to sweepai/logn/cache.py
• Rollback changes to docs/public/file_cache.py
• Rollback changes to docs/pages/blogs/file-cache.mdx

This is an automated message generated by Sweep AI.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sweep-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 19, 2024 6:34pm

[sweep-nightly]

Apply Sweep Rules to your PR?

• Apply: We should use loguru for error logging. If the log is inside an exception, use logger.exception to add tracebacks, where logger is imported from loguru. Use f-strings for string formatting in logger calls (e.g. logger.info(f'Hello {name}') instead of logger.info('Hello {name}', name=name)).
• Apply: There should be no debug log or print statements in production code.
• Apply: All functions should have parameters and output annotated with type hints. Use list, tuple and dict instead of typing.List, typing.Tuple and typing.dict.
• Apply: Leftover TODOs in the code should be handled.
• Apply: All new business logic should have corresponding unit tests in the same directory. For example, sweepai/api_test.py tests sweepai/api.py. Use unittest and unittest.mock as required.
• Apply: Any clearly inefficient or repeated code should be optimized or refactored.
• Apply: Remove any comments before code that are obvious. For example # this prints hello world; print('hello world').

This is an automated message generated by Sweep AI.