-
Notifications
You must be signed in to change notification settings - Fork 469
Add chat history support to web chat app #1363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
520165f
Add chat history
EricLBuehler a2e2d64
Support renaming
EricLBuehler af44235
Start immediately with new chat
EricLBuehler 58e2fa4
Add timestamp
EricLBuehler 0e14d97
Prettier chat list
EricLBuehler ff997ed
Style
EricLBuehler 83fff70
Delete chat
EricLBuehler 1ecbd89
Fix copy button
EricLBuehler a7dee36
Fix markdown rendering
EricLBuehler d8fa686
Store things in cache
EricLBuehler 25a9369
Store things in cache
EricLBuehler File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,3 +4,4 @@ | |
| *.a | ||
| .DS_Store | ||
| .idea | ||
| mistralrs-web-chat/cache | ||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Verify chrono version for security updates.
The chrono dependency looks good for timestamp handling. Please verify you're using a recent stable version without known vulnerabilities.
🌐 Web query:
💡 Result:
Based on the search results, I can provide information about the chrono crate for Rust.
The latest stable version of the chrono crate appears to be 0.4.38, which was released on December 9, 2024, according to the GitHub releases information[2]. This release brought approximately 20% improvement to the performance of the formatting code and added a convenient
days_sincemethod for theWeekdaytype[2].Regarding security advisories for version 0.4.41, there is no specific information about this version in the search results. However, the search results do mention past security advisories for the chrono crate:
In November 2020, CVE-2020-26235 and RUSTSEC-2020-0071 were opened against the time crate, which chrono depended on. This was later made into a security advisory against chrono as RUSTSEC-2020-0159[6][9]. The issue was related to calls to
localtime_rbeing potentially unsound[6][9].Since version 4.20, chrono no longer uses
localtime_rand instead uses Rust code to query the timezone, addressing the previous security concerns[6][9]. Additionally, chrono has been working to remove its dependency on time 0.1, which had unaddressed security vulnerabilities. This change was implemented in chrono 0.4.30[9].Without more recent information specifically about version 0.4.41, I cannot confirm whether there are any security advisories for that particular version.
Citations:
Confirm and pin chrono crate version
chrono = "0.4.41", but crates.io’s latest published stable release is0.4.38(December 9, 2024).0.4.41has actually been released; otherwise, change this to"0.4.38".🤖 Prompt for AI Agents