Skip to content
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

comment out the per doc sync hack #3620

Merged
merged 2 commits into from
Jan 7, 2025
Merged

Conversation

rkuo-danswer
Copy link
Contributor

Description

reverting the hack used to mitigate repeated doc sync.

How Has This Been Tested?

[Describe the tests you ran to verify your changes]

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

  • This PR should be backported (make sure to check that the backport attempt succeeds)

@rkuo-danswer rkuo-danswer marked this pull request as ready for review January 7, 2025 19:05
Copy link

vercel bot commented Jan 7, 2025

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

Name Status Preview Comments Updated (UTC)
internal-search ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 7, 2025 7:14pm

@rkuo-danswer rkuo-danswer enabled auto-merge January 7, 2025 19:20
@rkuo-danswer rkuo-danswer added this pull request to the merge queue Jan 7, 2025
Merged via the queue into main with commit 7cd76ec Jan 7, 2025
13 checks passed
@rkuo-danswer rkuo-danswer deleted the bugfix/revert_doc_sync branch January 9, 2025 00:37
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