Skip to content

Misc Changes from Async Question Images PR, Clear Profile Cache, PFP Upload Protections#476

Merged
AdamFipke merged 5 commits intomainfrom
adam/async-pr-refactor/misc-changes
Feb 24, 2026
Merged

Misc Changes from Async Question Images PR, Clear Profile Cache, PFP Upload Protections#476
AdamFipke merged 5 commits intomainfrom
adam/async-pr-refactor/misc-changes

Conversation

@AdamFipke
Copy link
Collaborator

@AdamFipke AdamFipke commented Feb 12, 2026

Description

I'm cannibalizing #259 and splitting it into multiple PRs. For context, back then I assumed I would've had that all merged before things got busy, so I made a bunch of misc changes in that PR that should've been its own thing. Here's some of them.

Small refactor of Advanced Settings and addition of a Clear Profile Cache button

image

Before it used a submenu. While I did like it, I kinda just wanted to have one unified "Advanced Settings" page since that's how other sites do it, but these changes/differences are also very small so it doesn't really matter that much.
image

Fix course preference table

Before
image

After
image

Add a new "name" field when manually creating a chunk

image

Previously, all manually inserted chunks were always "Manually Inserted Information" for their 'name' field, this just lets them customize it. You could always edit it after the fact

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • This requires a run of yarn install
  • This change requires an addition/change to the production .env variables. These changes are below:
  • This change requires developers to add new .env variables. The file and variables needed are below:
  • This change requires a database query to update old data on production. This query is below:

How Has This Been Tested?

Manually tested the changes.

Checklist:

  • I have performed a code review of my own code (under the "Files Changed" tab on github) to ensure nothing is committed that shouldn't be (e.g. leftover console.logs, leftover unused logic, or anything else that was accidentally committed)
  • I have commented my code where needed
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked that new and existing tests pass locally with my changes
  • Any work that this PR is dependent on has been merged into the main branch
  • Any UI changes have been checked to work on desktop, tablet, and mobile

@AdamFipke AdamFipke requested a review from bhunt02 February 12, 2026 23:40
@AdamFipke AdamFipke changed the title Async Question Images PR Refactor: Misc Changes, Clear Profile Cache, PFP Upload Protections Misc Changes from Async Question Images PR, Clear Profile Cache, PFP Upload Protections Feb 12, 2026
Copy link
Collaborator

@bhunt02 bhunt02 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pretty good, some comments, re-request me when you've reviewed

label="Coordinator Email"
name="coordinatorEmail"
tooltip="Email of the coordinator of the course"
tooltip="Email of the coordinator/instructor of the course"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i love these random flavor text changes in every PR

documentText: values.content,
metadata: {
name: 'Manually Inserted Information',
name: values.name || 'Manually Inserted Information',
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm anticipating merge conflicts with my vector store refactor... sigh... that's what i get for having a PR that is old

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

THANK. YOU.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it might be abusable though depending on your route

label: 'Chatbot History',
children: <UserChatbotHistory />,
},
{
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i thought having it as a family of options might've been useful, the dropdown also prevented it from being shown by default (comparable to other advanced settings in similar webapps)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's about the same UX either way (plus it's a rare usecase), but I could change it back if you'd prefer. Also I'm not entirely sure I know what you mean by the dropdown preventing it from being shown by default?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC, the advanced options would only show when highlighted or selected. ants is weird tho and i cant remember exactly

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I believe before it was a submenu, where you click Advanced -> submenu with [Access Tokens, Clear Cache] -> Click on item and taken to dedicated page for that item.

What I did here was just make one "Advanced" page with both Access Tokens and Clear Cache on the same page, which I guess is shown on the screenshots in the PR description. It's basically the same, maybe just a little more consistent with our profile settings pages but it's kinda subjective.

}
}

@Delete('/clear_cache')
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

throttle/rate limit on this please...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just in case yaknow

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, i'll put like 5 calls allowed per 5 minutes should be good i think

@AdamFipke AdamFipke requested a review from bhunt02 February 24, 2026 00:53
Copy link
Collaborator

@bhunt02 bhunt02 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AdamFipke AdamFipke merged commit e2c173b into main Feb 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants