René's URL Explorer Experiment


Title: fix(connectors): count hard-kill failures and cap deletion blast radius by waleedlatif1 · Pull Request #6909 · simstudioai/sim · GitHub

Open Graph Title: fix(connectors): count hard-kill failures and cap deletion blast radius by waleedlatif1 · Pull Request #6909 · simstudioai/sim

X Title: fix(connectors): count hard-kill failures and cap deletion blast radius by waleedlatif1 · Pull Request #6909 · simstudioai/sim

Description: Two coupled fixes from a pipeline audit. Both address failures that are currently invisible: one makes a crashing connector self-report, the other stops a healthy-looking listing from destroying a corpus. Why a crashing connector never backs off An OOM is a SIGKILL, so executeSync's catch and finally never run. The out-of-process stale-lock reaper is the only survivor — and it cleared the lock without ever incrementing consecutiveFailures. MAX_CONSECUTIVE_FAILURES was therefore structurally unreachable for hard kills, the exact failure mode that most needs it, and the reaper's flat 10-minute retry is shorter than any healthy sync interval. A connector that dies hard is retried more aggressively than a working one, forever, without ever recording a failure. The observed ~2-hour crash cadence in production is the stale-lock TTL, not any connector's schedule. The failure threshold and backoff ladder move to sync-limits.ts. Two writers of one policy with no shared constant is exactly how the drift arose. The reaper now increments, backs off, and disables in the same statement that clears the lock. A read-then-write loses increments when two cron ticks overlap. Shape follows the existing schedule-execution.ts precedent. Sync-log rows left started by a killed run are now swept. Nothing else ever reconciles them, and loadPreviousListingObservation reads only completed rows — so a never-closed run silently ages out the observation it should have provided. The sweep keys off each row's own startedAt, not this tick's reclaims. A row orphaned before this ships belongs to a connector already flipped out of syncing and would never appear in a future reclaim batch. Scoped to the tick, the fix could not heal the backlog that already exists. The finally block is deleted — every exit path set its flag, and a SIGKILL skips finally regardless, so it read as a crash safety net that could never fire. A lock-contended run now reports as skipped rather than as a successful zero-document sync. lastSyncAt is no longer stamped on the failure path; it should mean last successful sync, and lastSyncError already carries the other meaning. Why a partial outage deletes half a corpus Every existing guard asks whether a listing looks broken. The collapse heuristic only fires below ~10% of the corpus, which leaves the entire 10–100% band unguarded. A source returning half its documents — one shard down, one folder's permissions changed — produces a listing that looks perfectly healthy: sync one tombstones the missing half, sync two hard-deletes it with embeddings and tags. Two intervals, no guard involvement. The same is true of any change to a connector's externalId derivation: a complete, correct listing of entirely new keys, under which every stored document is "absent." A pass whose deletions exceed a share of the corpus is held, all-or-nothing. Deleting up to a cap still destroys data and leaves a state no operator asked for. fullSync remains the documented escape hatch. A userExcluded document is never deletion-eligible. Guarded at deletion eligibility rather than at the select: filtering it out of the tombstoned read would also withhold resurrection, and since the connector listing and the restore mutation both require deletedAt IS NULL, that would strand the row permanently — invisible, unrestorable, and undeletable. Listed documents are counted over the same population as the owned count. seenExternalIds is populated before the excluded short-circuit, so comparing it against a denominator that excludes those rows inflated the ratio and weakened the collapse guard. resolvePreviousOwnedCount judges the previous run against a corpus at least as large as the one present. lastSyncDocCount counts only visible documents, so after a tombstoning pass it collapsed toward zero and corroboration became impossible. Ordering note for reviewers: that last item un-jams the two-strike purge, which is currently stuck shut by accident. It ships in the same commit as the cap deliberately — landing it alone would re-open the destruction path the cap exists to close. Verification type-check clean · check:audits 32/32 · 1003 connector tests · 8 route tests (the scheduler route had no test file before this). 72 mutations applied, all red on their intended test, none inert. Including: re-coupling the sync-log sweep to the tick's reclaims, reinstating the flat 10-minute retry, reverting the numerator asymmetry, restoring the select-level exclusion filter, and swapping the backoff SQL's multiplication for addition, which would retry every connector at a flat 31 minutes forever. One existing test asserted the pre-fix behavior (touches no sync-log rows when nothing was reclaimed) and was replaced with its inverse rather than left in place. Known and deliberate Root cause behind three of these findings: the in-process fallback path is unbounded. When Trigger.dev is unavailable, dispatchSync runs executeSync fire-and-forget in the web process with no maxDuration, so such a run can outlive the 2h stale-lock TTL and still hold write authority after the reaper has reclaimed the connector and dispatched a replacement. The guards added here — status = 'started' on completeSyncLog, status = 'syncing' on both terminal connector writes — make the reclaim authoritative so a superseded run cannot corrupt state. They do not stop two runs reconciling the same corpus concurrently. Bounding or heartbeating the fallback path is the real fix and is deliberately out of scope here. A connector paused mid-sync is no longer flipped back to active by the completing run. That falls out of the same status = 'syncing' guard and is intended: the pause write does not check current status, so today a completing run silently un-pauses it. A running sync heartbeats its lock, so the TTL means "nobody is working on this" rather than "this started a long time ago". The reclaim increments consecutiveFailures, and a reclaimed run's terminal write — including its consecutiveFailures reset — is rejected. For the in-process fallback path, which has no duration cap, that made the reaper a one-way ratchet: a large self-hosted sync that legitimately outran the 2h TTL was counted as a failure it could never clear, and ten of them disabled a connector whose every sync had actually succeeded. A live run now refreshes updatedAt every 5 minutes so the reclaim predicate never matches it. The beat is guarded on the run's own sync_lock_token, so it doubles as an ownership probe: a run that has lost its lock aborts instead of doing hours more work and writing documents alongside its replacement. A run that stops beating is genuinely dead or wedged, and reclaiming it stays correct. The deletion cap gates the two generations separately. Summing soft and hard deletes against one cap double-counted: hard deletes are the previous generation's soft deletes, already gated by the same cap once. On a connector with steady churn that ratcheted shut — 1,000 documents at 15% churn against a cap of 250 applied 150 soft on sync 1, then requested 150 soft + 150 hard on sync 2, exceeded the cap, and the all-or-nothing hold blocked the very hard deletes that would have drained the backlog, which then grew forever. Each generation is now capped against the same ceiling, which keeps the per-sync blast radius bounded without the deadlock. The outage and externalId-change shapes are unaffected: both are a single oversized soft generation. Terminal writes are guarded on an ownership token, not just on status. status = 'syncing' asserts that a run holds the lock, not that this run does. Once the reaper reclaims a stale lock and the scheduler dispatches a replacement, the replacement sets syncing again — so the original run matched, overwrote the replacement's in-flight state and the reclaim's bookkeeping, and then had the replacement's own write rejected as superseded. The dead run won and the live one lost, which is worse than the unguarded last-write-wins it replaced. knowledge_connector.sync_lock_token is written in the same CAS that takes the lock (and reused as the sync-log row id, so the connector points at the run holding it), matched by both terminal writes, and cleared on release. The migration is additive, nullable, and unbackfilled: existing rows read NULL, which no in-flight run can match, so a sync spanning the deploy simply has its terminal write skipped and is re-run by the scheduler. Rejected updatedAt as an optimistic-concurrency token: performUpdateKnowledgeConnector stamps updatedAt on every connector update with no status guard, so a user editing config mid-sync would poison the token, the terminal write would be rejected, and the connector would sit syncing until the reaper cleared it two hours later — worse than the bug being fixed. Both terminal writes go through a single writeTerminalConnectorState, which applies the stillHoldsSyncLock WHERE internally. Callers pass only their SET values and never build a WHERE clause, so there is exactly one place the guard can be removed from — and a unit test on that function's emitted WHERE catches its removal. A terminal path added later cannot forget the guard, because there is no unguarded way to write the row. The pre-lock "knowledge base deleted" write is deliberately outside it: that run never acquired the lock, so a status = 'syncing' guard would silently discard the error it needs to record. A superseded run's document writes still persist. Documents it added, updated, resurrected, or deleted are already committed and are not rolled back — only the connector-level bookkeeping (status, lastSyncAt, failure counter, nextSyncAt) is discarded, in favour of whoever reclaimed the row. An operator sees the connector carrying the reaper's verdict, the sync-log row failed, and the task run reporting sync_superseded, while the corpus reflects the work that run actually did. The failure path deliberately does not get the sync_superseded outcome. result.error there already carries the real failure cause and the task wrapper already reports the run as unsuccessful, so overwriting it would destroy the diagnostic without changing the reported outcome; the supersession is carried by a warn log instead. Two tests in route.test.ts were inert and were rewritten rather than left: one asserted node.column === …connectorId, but eq() builds {left, right} and only inArray() builds {column}, so an eq-scoped sweep passed it; the other asserted only the bookends of the disable expression, leaving the comparison itself unchecked, so + 2 >=, + 1 >, and an inverted + 1 <= all passed — the last disabling a connector on its first hard kill. Both now pin the whole expression and are mutation-checked against those specific mutants. A second test-quality pass replaced two assertions that could not fail. The backoff-ladder test recomputed Math.min(failures * step, cap) from the SQL's own binds and compared it against connectorFailureBackoffMinutes — both sides derived from the same two constants, so it held for any values and any shape. It now pins the SQL text whole, pins the binds to the shared constants, and pins concrete minutes on both sides (1 → 30, 3 → 90, 9 → 270, 48 → 1440, 49 → 1440), so the SQL↔JS equivalence is asserted rather than assumed. The hold-notice test used three independent toContain calls on distinct digit strings, which passed with the first two interpolations swapped — an inverted, actively misleading operator message — and now asserts the message whole. The in-process failure path is extracted as buildSyncFailureUpdate, mirroring buildSyncSuccessUpdate, so the auto-disable threshold, the backoff, and the token release are unit-tested on the path the breaker actually runs through. Previously only the reaper's SQL equivalent was covered. Ceiling on what the WHERE-clause assertions prove: packages/testing/src/mocks/schema.mock.ts maps every column to its bare name, so knowledgeConnector.status and knowledgeConnectorSyncLog.status are both the string 'status'. Assertions of the form node.left === schemaMock.

.are therefore table-blind — a guard on the wrong table would still pass. No test here depends on that distinction, and the shared mock is deliberately not churned in this PR, but the next person should know the limit. loadPreviousListingObservation reconstructs the previous listing from stored counters, and excluded documents land in docsUnchanged, so that historical figure stays inflated. Not recoverable without a schema change; errs toward blocking deletions, so it fails safe — and the new blast-radius cap is now a second line of defense behind it. Closing it as a documented limitation rather than carrying it as an open item. If completeSyncLog(…, 'completed') succeeds and a later step throws, the catch path's failed write now no-ops rather than flipping the row. A behavior change beyond the reported bug, and an improvement: the row's counters do describe a completed listing-and-reconciliation pass, and loadPreviousListingObservation reads only completed rows, so it now receives an observation it previously lost. sync-engine.test.ts moved from a local vi.mock('drizzle-orm') stub to the shared drizzleOrmMock. The new guard assertions need real condition nodes rather than bare vi.fn()s, and the local stub was also incomplete — it omitted six operators the module imports and only worked because no test reached them. All 113 tests pass against the shared mock.

Open Graph Description: Two coupled fixes from a pipeline audit. Both address failures that are currently invisible: one makes a crashing connector self-report, the other stops a healthy-looking listing from destroying a ...

X Description: Two coupled fixes from a pipeline audit. Both address failures that are currently invisible: one makes a crashing connector self-report, the other stops a healthy-looking listing from destroying a ...

Opengraph URL: https://github.com/simstudioai/sim/pull/6909

X: @github

direct link

Domain: github.com

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf
route-pattern/:user_id/:repository/pull/:id/files(.:format)
route-controllerpull_requests
route-actionfiles
fetch-noncev2:0086afc6-19b7-0e83-7808-f940db4f966a
current-catalog-service-hashae870bc5e265a340912cde392f23dad3671a0a881730ffdadd82f2f57d81641b
request-idE668:1AE782:5FE725:8607A3:6AFB62F8
html-safe-noncef6c6a4e36a451797f6fba71e9e8a29cee3ae8a3ebde756ca4ff88cc2bde9c1d9
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFNjY4OjFBRTc4Mjo1RkU3MjU6ODYwN0EzOjZBRkI2MkY4IiwidmlzaXRvcl9pZCI6IjU2NjQ3NDg2ODA0OTg2MDI3NDUiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmac20dfc4687e37afc0465bc6df8513e30ddaceb6714a9099eb9525217eb528b2c7
hovercard-subject-tagpull_request:4327498910
github-keyboard-shortcutsrepository,pull-request-list,pull-request-conversation,pull-request-files-changed,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///pull_requests/show/files
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/simstudioai/sim/pull/6909/files
twitter:imagehttps://avatars.githubusercontent.com/u/40672544?s=400&v=4
twitter:cardsummary_large_image
og:imagehttps://avatars.githubusercontent.com/u/40672544?s=400&v=4
og:image:altTwo coupled fixes from a pipeline audit. Both address failures that are currently invisible: one makes a crashing connector self-report, the other stops a healthy-looking listing from destroying a ...
og:site_nameGitHub
og:typeobject
hostnamegithub.com
expected-hostnamegithub.com
Noneea33d13c96d0ff66bd8fa906b193d2213536b78cb06b0c50a4632c58b1418f94
turbo-cache-controlno-preview
diff-viewunified
go-importgithub.com/simstudioai/sim git https://github.com/simstudioai/sim.git
octolytics-dimension-user_id199344406
octolytics-dimension-user_loginsimstudioai
octolytics-dimension-repository_id912559512
octolytics-dimension-repository_nwosimstudioai/sim
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id912559512
octolytics-dimension-repository_network_root_nwosimstudioai/sim
turbo-body-classeslogged-out env-production page-responsive full-width
disable-turbotrue
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release59ef97164c52cf59bd10558ddec9c4f482763988
ui-targetfull
theme-color#1e2327
color-schemelight dark

Links:

Skip to contenthttps://github.com/simstudioai/sim/pull/6909/files#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fsimstudioai%2Fsim%2Fpull%2F6909%2Ffiles
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fsimstudioai%2Fsim%2Fpull%2F6909%2Ffiles
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fpull_requests%2Fshow%2Ffiles&source=header-repo&source_repo=simstudioai%2Fsim
Reloadhttps://github.com/simstudioai/sim/pull/6909/files
Reloadhttps://github.com/simstudioai/sim/pull/6909/files
Reloadhttps://github.com/simstudioai/sim/pull/6909/files
simstudioaihttps://github.com/simstudioai
simhttps://github.com/simstudioai/sim
Codehttps://github.com/simstudioai/sim
Issues129 (129)https://github.com/simstudioai/sim/issues
Pull requests197 (197)https://github.com/simstudioai/sim/pulls
Actionshttps://github.com/simstudioai/sim/actions
Projectshttps://github.com/simstudioai/sim/projects
Security and qualityhttps://github.com/simstudioai/sim/security
Insightshttps://github.com/simstudioai/sim/pulse
Sign up for GitHub https://github.com/signup?return_to=%2Fsimstudioai%2Fsim%2Fissues%2Fnew%2Fchoose
terms of servicehttps://docs.github.com/terms
privacy statementhttps://docs.github.com/privacy
Sign inhttps://github.com/login?return_to=%2Fsimstudioai%2Fsim%2Fissues%2Fnew%2Fchoose
waleedlatif1https://github.com/waleedlatif1
staginghttps://github.com/simstudioai/sim/tree/staging
fix/sync-corehttps://github.com/simstudioai/sim/tree/fix/sync-core
Conversation 46 https://github.com/simstudioai/sim/pull/6909
Commits 14 https://github.com/simstudioai/sim/pull/6909/commits
Checks 30 https://github.com/simstudioai/sim/pull/6909/checks
Files changed https://github.com/simstudioai/sim/pull/6909/files
Please reload this pagehttps://github.com/simstudioai/sim/pull/6909/files
fix(connectors): count hard-kill failures and cap deletion blast radius https://github.com/simstudioai/sim/pull/6909/files#top
Show all changes 14 commits https://github.com/simstudioai/sim/pull/6909/files
a2f8eab fix(connectors): count hard-kill failures and cap deletion blast radius waleedlatif1 Aug 20, 2026 https://github.com/simstudioai/sim/pull/6909/commits/a2f8eab30a4ae5939a08492add4d8e599dc511ce
d3716ed fix(connectors): surface a held reconciliation and scope the cap to e… waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/d3716ed40a86584627d1767a061663f5b74e38b0
8e3185a fix(connectors): stop a reclaimed run from overwriting the reaper's v… waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/8e3185aee92c69bbe5de4c671b51b5c92edc9e10
a5e515f fix(connectors): identify which run holds a connector's sync lock waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/a5e515f18e6be4f57f2015d123f6e601ade00c18
81c7b23 fix(connectors): heartbeat a running sync and cap deletion generation… waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/81c7b239a6fe764d22ca0ba12c03a6a8a96ada01
e30ade9 test(connectors): pin the failure ladder on both sides and cover the … waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/e30ade9c684419d6aafada55c6ea8a57dfee7a3c
5c419ce chore(db): regenerate the sync lock token migration with drizzle-kit waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/5c419cea0f575998f0caaef89b0145d61fe79ae9
4b98668 fix(connectors): make the sync-log sweep aware of a live run's heartbeat waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/4b98668c5d4f6d1f25cce5373a611f482610d5c0
9fada81 fix(connectors): require a lock to be held, owned, and heartbeated be… waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/9fada813a3f98178c84dfd84f090eacfcb35edae
6eaeffe fix(connectors): heartbeat every unbounded phase, not just the batch … waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/6eaeffe6b6b0ee40e68e7550ce4b1aa866e5198b
d4a3ddb chore(db): regenerate the sync lock token migration as 0298 waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/d4a3ddb09f7fcb6707c1dde0922b22eb15150640
aeb0ae5 fix(knowledge): guard the document lifecycle and cap retry dispatches waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/aeb0ae5324ea8e1acfecfc0c6e632891767b0fc0
d4895da fix(knowledge): recover stranded documents and split the sync lock lease waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/d4895da1ac9167d35c4f80f77ce6df7d4e798ed4
712b2c4 fix(knowledge): guard the completed sync log and free a deleted run's… waleedlatif1 Aug 21, 2026 https://github.com/simstudioai/sim/pull/6909/commits/712b2c425c9a5cd001c64bae60f8580918c0f4ae
Clear filters https://github.com/simstudioai/sim/pull/6909/files
Please reload this pagehttps://github.com/simstudioai/sim/pull/6909/files
Please reload this pagehttps://github.com/simstudioai/sim/pull/6909/files
route.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-aba6632dfaf0a75a450f1d705cf679d0f3a114e076a7a1f87b4299f13efaa3b6
route.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-160cf59161140d9fa0b08e1342a3077291ed72ffa7968f68277622c636eea42e
route.ts https://github.com/simstudioai/sim/pull/6909/files#diff-a726e0b535eca765a3dedb1e1b73bcf3fbf19d74c743d9bb5722da53fdeb473d
utils.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-23b670a77c544ff5ccc0c31dd1c6700ef269c8eddeaddc29039f960c17ca2ac6
route.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-bc1347c09a923475eddb3d80f9a52ad1fd9aa0b23a8d8a89943d98ff941469ba
route.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-433caeb5818d865b3c85af8c1d53da265115f49e84f44d3bc400d89b715a4811
route.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-2b95ef7c7ebb2aafe5dee7ffe292c5784e965540fb30c25a60348114c0296fa2
utils.ts https://github.com/simstudioai/sim/pull/6909/files#diff-c7ffeadf9513e45920cd397c18d4b5f4e8f0cb1350a297222cbb3effd05adb4c
store.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-baca515097f15c7777418f747d100ebc65c07a9011e2b588c1c8935c96b4ab06
copy-files.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-31d6b823ee537f678640acbf005d7c2e0cdbe039addabcf822609e39aff913a1
query.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-06090aae24989d4b76bdf069533f4734ae040dcb1cd511f75f0a56ed4688f5a1
usage-log.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-4f1308a51ea50378ff81bd88b25b7ae18abbbab8272edcaa44de31c8b4ae19d9
invoices.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-c340dec878362883cadfd3a1950a7b6aecb3acfd9a571666173b67355684d2f4
add-workspace-files.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-cd55213a4ee8d91bc320a1bfe765efd76f299cd5f6e9dbb5dea17643e9cfee64
add-workspace-files.ts https://github.com/simstudioai/sim/pull/6909/files#diff-46159b55a823bbe7f57e8fe05bda3b42236c497a0f7441d826f6f53bebb2fa7b
documents.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-5e8dd6a21ba53fad9ffd25e17795bc3daee65d49d0a6cd2947c8a24d4f0f94c1
documents.ts https://github.com/simstudioai/sim/pull/6909/files#diff-d653b2ae68fa0a4109a0a869b7830894cf5eaaa5284416c04f31d742ec5aae08
upload-sessions.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-59d466d0ecbc21a456933e27d8a9bd428a196d70c5f5a2f73e2999afd0c33dd1
upload-sessions.ts https://github.com/simstudioai/sim/pull/6909/files#diff-bde8ef7aea68c8dd825030263123061cf0eba2a11e3db0dd02c3c1edf6163589
queue.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-6ea21bcc90345a76b17c89a5a511c774cd781e37b26549691e1e098bcb115bb0
queue.ts https://github.com/simstudioai/sim/pull/6909/files#diff-11e8be841a5a3833bbbcd7c36e0582314f138251db9cd030600ea5774b49177d
sync-engine.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-021afebf7e100833ecdc940e307263436964ce85ef3dfd40fc90307a1d115534
sync-engine.ts https://github.com/simstudioai/sim/pull/6909/files#diff-277f76464f02682e44e6de58ebd215c927f0f6a3a7165af669a0717b593790e9
sync-limits.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-7f44c2a0d2b282bfe23a446e49449d04324d117994fc5af450b17260b1f81c2e
sync-limits.ts https://github.com/simstudioai/sim/pull/6909/files#diff-e4bf8fcfa2c3e67b5a9397f0c335534269a6b2c57dcf85c5fa4191a1f414811e
document-indexing-usage.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-ff4ae625d37edbdfb8ea953b69b76e91faa6761157ff50400a5242c5ef120577
document-processing-source.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-5b6e93417c23c69dd607283ad630cf19fce90751f3480053378e133760b97633
processing-claim.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-f6def3f6b770693edff4a4bba0e5fec5e233325d49bfced2bffcea6a30ff1bd0
processing-claim.ts https://github.com/simstudioai/sim/pull/6909/files#diff-4eaea67e7e685e74770466d445af7cb96900ed21ae6682513bf40ed287787544
processing-dispatch.ts https://github.com/simstudioai/sim/pull/6909/files#diff-2a18c1380459b60eada8c819ca52be4e3d1882b1d7c7913be14831b0b7e158f1
processing-queue.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-61f9b64ff566f2114b69c46afe5ee47845d13fc0758de1de3797e5322c2b1fad
retry-processing-grace.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-24e9b3a40786dff73fbb7dc3d959893039829339609677b1b55c06fd4f2ccddd
service.ts https://github.com/simstudioai/sim/pull/6909/files#diff-12adff6ec055d413ec20f1debed4ca207b994d23df6de9aa4ef79bf47f2857b2
tag-filter.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-a091a3a6449b4a161156002367852135bb69d4592e8e2401ccc4221a77c3df72
types.ts https://github.com/simstudioai/sim/pull/6909/files#diff-16ad70e3cf91cc32c37134c43b4b5f020173e5bf81e0c93c7b7447cc5f9b2de8
connectors.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-ad352d1373d2052001dc8af9e95b9f27467ea46cd5014040c43765b19b980955
connectors.ts https://github.com/simstudioai/sim/pull/6909/files#diff-50cb99189b1dc87df12d9b4f50a563206952b53de947873de00ad9f30ef59a25
documents.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-db66971f8d0b866eb89387fc25e3657cc312f95fd71f56f9bfa086e2f7bcf3ac
documents.ts https://github.com/simstudioai/sim/pull/6909/files#diff-a52cfed82ffc18be4a3578b656d5b30db89d99b0842447dd256cbc40d16736cf
track-chat-upload.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-fc551b1b39c7033e277ea1693d0e788c119dad93bde742a29ad55d5be16afe2a
workspace-file-secret-provenance.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-a135e689defc3929a9b013c97cea9f63ba19913b4bba84a760d2ea5399dcd920
path-claims.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-d8dc729e9d70e3e9a87f48c44ec917d725b577e61e430b248102d3a0d659c402
human-in-the-loop-manager.test.ts https://github.com/simstudioai/sim/pull/6909/files#diff-72580e5e18315802c8260c3c01abd48ff8de248edd72c9890764c158e0e52478
0298_nosy_ken_ellis.sql https://github.com/simstudioai/sim/pull/6909/files#diff-0bed31d16d4059693e772a328b058dbf57b2dd54c8ef255b2f38a131fb4e93b9
0298_snapshot.json https://github.com/simstudioai/sim/pull/6909/files#diff-0498516e7d61bfbf18d7fa066e8656009bdd6fdcdcebc4709ec4c1b95fe418da
_journal.json https://github.com/simstudioai/sim/pull/6909/files#diff-37150cc65ad16ee6fbc5fa318fc096be7730e16d63eaf863e3df5521b7030649
schema.ts https://github.com/simstudioai/sim/pull/6909/files#diff-9a959e2ce3cb4c86957bbae021d06eae364f7b0cb18964f5873bab53220af928
schema.mock.ts https://github.com/simstudioai/sim/pull/6909/files#diff-3b648ee44a059e5fc069169fdfd7c32c89200a3e79b5d0dc25227d3470da73af
apps/sim/app/api/copilot/feedback/route.test.tshttps://github.com/simstudioai/sim/pull/6909/files#diff-aba6632dfaf0a75a450f1d705cf679d0f3a114e076a7a1f87b4299f13efaa3b6
View file https://github.com/simstudioai/sim/blob/712b2c425c9a5cd001c64bae60f8580918c0f4ae/apps/sim/app/api/copilot/feedback/route.test.ts
Open in desktop https://desktop.github.com
https://github.co/hiddenchars
https://github.com/simstudioai/sim/pull/6909/{{ revealButtonHref }}
https://github.com/simstudioai/sim/pull/6909/files#diff-aba6632dfaf0a75a450f1d705cf679d0f3a114e076a7a1f87b4299f13efaa3b6
https://github.com/simstudioai/sim/pull/6909/files#diff-aba6632dfaf0a75a450f1d705cf679d0f3a114e076a7a1f87b4299f13efaa3b6
apps/sim/app/api/knowledge/connectors/sync/route.test.tshttps://github.com/simstudioai/sim/pull/6909/files#diff-160cf59161140d9fa0b08e1342a3077291ed72ffa7968f68277622c636eea42e
View file https://github.com/simstudioai/sim/blob/712b2c425c9a5cd001c64bae60f8580918c0f4ae/apps/sim/app/api/knowledge/connectors/sync/route.test.ts
Open in desktop https://desktop.github.com
Please reload this pagehttps://github.com/simstudioai/sim/pull/6909/files
apps/sim/app/api/knowledge/connectors/sync/route.tshttps://github.com/simstudioai/sim/pull/6909/files#diff-a726e0b535eca765a3dedb1e1b73bcf3fbf19d74c743d9bb5722da53fdeb473d
View file https://github.com/simstudioai/sim/blob/712b2c425c9a5cd001c64bae60f8580918c0f4ae/apps/sim/app/api/knowledge/connectors/sync/route.ts
Open in desktop https://desktop.github.com
https://github.co/hiddenchars
https://github.com/simstudioai/sim/pull/6909/{{ revealButtonHref }}
https://github.com/simstudioai/sim/pull/6909/files#diff-a726e0b535eca765a3dedb1e1b73bcf3fbf19d74c743d9bb5722da53fdeb473d
https://github.com/simstudioai/sim/pull/6909/files#diff-a726e0b535eca765a3dedb1e1b73bcf3fbf19d74c743d9bb5722da53fdeb473d
https://github.com/simstudioai/sim/pull/6909/files#diff-a726e0b535eca765a3dedb1e1b73bcf3fbf19d74c743d9bb5722da53fdeb473d
Please reload this pagehttps://github.com/simstudioai/sim/pull/6909/files
Please reload this pagehttps://github.com/simstudioai/sim/pull/6909/files
https://github.com/simstudioai/sim/pull/6909/files#diff-a726e0b535eca765a3dedb1e1b73bcf3fbf19d74c743d9bb5722da53fdeb473d
apps/sim/app/api/knowledge/utils.test.tshttps://github.com/simstudioai/sim/pull/6909/files#diff-23b670a77c544ff5ccc0c31dd1c6700ef269c8eddeaddc29039f960c17ca2ac6
View file https://github.com/simstudioai/sim/blob/712b2c425c9a5cd001c64bae60f8580918c0f4ae/apps/sim/app/api/knowledge/utils.test.ts
Open in desktop https://desktop.github.com
https://github.co/hiddenchars
https://github.com/simstudioai/sim/pull/6909/{{ revealButtonHref }}
https://github.com/simstudioai/sim/pull/6909/files#diff-23b670a77c544ff5ccc0c31dd1c6700ef269c8eddeaddc29039f960c17ca2ac6
https://github.com/simstudioai/sim/pull/6909/files#diff-23b670a77c544ff5ccc0c31dd1c6700ef269c8eddeaddc29039f960c17ca2ac6
apps/sim/app/api/mothership/chats/[chatId]/fork/route.test.tshttps://github.com/simstudioai/sim/pull/6909/files#diff-bc1347c09a923475eddb3d80f9a52ad1fd9aa0b23a8d8a89943d98ff941469ba
View file https://github.com/simstudioai/sim/blob/712b2c425c9a5cd001c64bae60f8580918c0f4ae/apps/sim/app/api/mothership/chats/%5BchatId%5D/fork/route.test.ts
Open in desktop https://desktop.github.com
https://github.co/hiddenchars
https://github.com/simstudioai/sim/pull/6909/{{ revealButtonHref }}
https://github.com/simstudioai/sim/pull/6909/files#diff-bc1347c09a923475eddb3d80f9a52ad1fd9aa0b23a8d8a89943d98ff941469ba
https://github.com/simstudioai/sim/pull/6909/files#diff-bc1347c09a923475eddb3d80f9a52ad1fd9aa0b23a8d8a89943d98ff941469ba
apps/sim/app/api/mothership/chats/read/route.test.tshttps://github.com/simstudioai/sim/pull/6909/files#diff-433caeb5818d865b3c85af8c1d53da265115f49e84f44d3bc400d89b715a4811
View file https://github.com/simstudioai/sim/blob/712b2c425c9a5cd001c64bae60f8580918c0f4ae/apps/sim/app/api/mothership/chats/read/route.test.ts
Open in desktop https://desktop.github.com
https://github.co/hiddenchars
https://github.com/simstudioai/sim/pull/6909/{{ revealButtonHref }}
https://github.com/simstudioai/sim/pull/6909/files#diff-433caeb5818d865b3c85af8c1d53da265115f49e84f44d3bc400d89b715a4811
https://github.com/simstudioai/sim/pull/6909/files#diff-433caeb5818d865b3c85af8c1d53da265115f49e84f44d3bc400d89b715a4811
apps/sim/app/api/resume/poll/route.test.tshttps://github.com/simstudioai/sim/pull/6909/files#diff-2b95ef7c7ebb2aafe5dee7ffe292c5784e965540fb30c25a60348114c0296fa2
View file https://github.com/simstudioai/sim/blob/712b2c425c9a5cd001c64bae60f8580918c0f4ae/apps/sim/app/api/resume/poll/route.test.ts
Open in desktop https://desktop.github.com
https://github.co/hiddenchars
https://github.com/simstudioai/sim/pull/6909/{{ revealButtonHref }}
https://github.com/simstudioai/sim/pull/6909/files#diff-2b95ef7c7ebb2aafe5dee7ffe292c5784e965540fb30c25a60348114c0296fa2
https://github.com/simstudioai/sim/pull/6909/files#diff-2b95ef7c7ebb2aafe5dee7ffe292c5784e965540fb30c25a60348114c0296fa2
https://github.com/simstudioai/sim/pull/6909/files#diff-2b95ef7c7ebb2aafe5dee7ffe292c5784e965540fb30c25a60348114c0296fa2
https://github.com/simstudioai/sim/pull/6909/files#diff-2b95ef7c7ebb2aafe5dee7ffe292c5784e965540fb30c25a60348114c0296fa2
apps/sim/app/api/v2/knowledge/utils.tshttps://github.com/simstudioai/sim/pull/6909/files#diff-c7ffeadf9513e45920cd397c18d4b5f4e8f0cb1350a297222cbb3effd05adb4c
View file https://github.com/simstudioai/sim/blob/712b2c425c9a5cd001c64bae60f8580918c0f4ae/apps/sim/app/api/v2/knowledge/utils.ts
Open in desktop https://desktop.github.com
https://github.co/hiddenchars
https://github.com/simstudioai/sim/pull/6909/{{ revealButtonHref }}
https://github.com/simstudioai/sim/pull/6909/files#diff-c7ffeadf9513e45920cd397c18d4b5f4e8f0cb1350a297222cbb3effd05adb4c
https://github.com/simstudioai/sim/pull/6909/files#diff-c7ffeadf9513e45920cd397c18d4b5f4e8f0cb1350a297222cbb3effd05adb4c
https://github.com/simstudioai/sim/pull/6909/files#diff-c7ffeadf9513e45920cd397c18d4b5f4e8f0cb1350a297222cbb3effd05adb4c
https://github.com/simstudioai/sim/pull/6909/files#diff-c7ffeadf9513e45920cd397c18d4b5f4e8f0cb1350a297222cbb3effd05adb4c
https://github.com/simstudioai/sim/pull/6909/files#diff-c7ffeadf9513e45920cd397c18d4b5f4e8f0cb1350a297222cbb3effd05adb4c
Please reload this pagehttps://github.com/simstudioai/sim/pull/6909/files
Please reload this pagehttps://github.com/simstudioai/sim/pull/6909/files
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.