crbench//

Mjolnir (Sonnet 5.5)

Latest run 2026-11-10-s1 · model mj-claude-sonnet-5-5

42%
Rating · High
95% 36%–47% · 1016 matchups
67.9%
Coverage
71.8%
Cross-File
24/37
Security
68% severity-weighted
96.8%
Validity
3.2%
False-alarms
127
Cases (100%)

Head-to-head — compare defect-by-defect

vs Claude Code (Opus 5.5)vs Cubicvs cursorvs Drape (Deep Review)vs Drape (Review)vs greptilevs Mjolnir (Opus 5.5)vs qodo

Coverage by severity — expand a row to see what it missed

critical 3/5 (60.0%)
The diff replaces the TOTP branch with `if (user.twoFactorEnabled && credentials.backupCode)`, which takes priority over TOTP verification, while the unchanged password gate above it verifies the password only when `totpCode` is falsy (`if (user.password && !credentials.totpCode)`). Posting an email, any non-empty `totpCode`, and a stolen backup code therefore skips the password check and authenticates on the backup code alone, without the password and without ever reaching TOTP verification.
maybeDoSizeFlush assigns `lastFile.Span.EndKey = newSpan.Key` without cloning, but newSpan.Key aliases the caller's reused scratch buffer in compactSpanEntry. The next WriteKey overwrites scratch in place, silently mutating the already-recorded EndKey and producing BackupManifest_File entries with overlapping/drifted spans (corrupted backup metadata). Sibling Reset paths in the same file clone correctly; maybeDoSizeFlush was missed.
high 82/108 (75.9%)
The deleteMany OR-arm `retryCount: { gt: 1 }` has no method or scheduledDate filter, so an SMS reminder retried more than once is deleted even when its scheduled date is still in the future, prematurely removing pending reminders.
scheduleSMS returns undefined on SMS-lock and throws on rate-limit/missing-creds; both paths increment retryCount, and the new deleteMany OR clause (retryCount > 1, with no method/date filter) permanently deletes those reminders after a few cron runs, so transient locks, monthly rate-limits, or a temporary Twilio misconfiguration silently drop reminders that previously stayed scheduled=false and were retried until scheduledDate.
In useBookings, this PR renames the instant-booking query parameter from bookingId (a number) to bookingUid (a string), but the getInstantBookingLocation query is still gated only on `enabled: !!bookingUid` with no isInstantMeeting guard. A non-instant "additional seats" booking flow carries a bookingUid in the URL (Booker store setSeatedEventData), so the query now fires for it; when the existing booking's metadata has a videoCallUrl, RedirectToInstantMeetingModal pushes the booker to that video page, and otherwise an error toast shows. Either way the seat cannot be booked. Before the rename the value was read as `parseInt(getQueryParam("bookingId") ?? "0")`, which was 0 (falsy, query disabled) on those URLs, so the rename is what newly triggers the path. The fix gates both the query and the redirect effect on isInstantMeeting.
The new date-override block is inserted ahead of the availability test that ends `checkIfIsAvailable` (`return busy.every(...)`). When a slot falls inside an override window the `find` callback sets `dateOverrideExist` and returns undefined, so `.find()` matches nothing, the outer branch is skipped, and `if (dateOverrideExist) return true` reports the slot bookable without ever evaluating `busy`. A slot inside a date override is offered even when it collides with an existing booking.
A race condition in BuildIndex allows multiple goroutines to concurrently build the same expensive index for the same key. This is caused by moving the b.cacheMu lock from protecting the entire function to only protecting the final cache assignment.
The new pod index `AddPodControllerUIDIndexer` / `PodControllerUIDIndex` keys solely on the owning controllerRef's UID (`[]string{string(ref.UID)}`), ignoring namespace, kind, and name. Controllers (DaemonSet/ReplicaSet/Job/StatefulSet) that look pods up through this index can claim the wrong pods when a stale or duplicated ownerReference UID collides. The fix re-keys the index on the full (namespace, kind, name, uid) tuple.
Passing `nextConfig: __NEXT_HAS_REWRITES ? undefined : nextConfig` to getNextPathnameInfo was meant to preserve the locale prefix, but disabling the whole config also disables basePath stripping. The `/_next/data/<buildId>/...` prefix is never removed, and on a catch-all route the route regex overwrites router.query.<param> with the leftover data-URL segments, producing malformed URLs and 404s when basePath + rewrites + middleware + dynamic routes combine.
When requests are authenticated with API keys or org auth tokens (which have user_id=None), organization_context.member is None. Line 71 attempts to access organization_context.member.has_global_access without checking if member is None, causing an AttributeError crash when optimized_pagination=true is used, even though the request passed all permission checks with valid org:write scope.
EventManager.ts:170 now writes credentialId: undefined for video booking references (was result.credentialId from videoClient.ts:78), so handleCancelBooking.ts:491's `if (bookingVideoReference.credentialId)` guard is always false and the external video meeting is never deleted on cancellation.
In listWithTeamHandler (packages/trpc/server/routers/viewer/eventTypes/listWithTeam.handler.ts), this PR adds `AND "public"."EventType"."teamId" IS NULL` to the WHERE clause of Part 1 of the raw SQL UNION query. Part 1 previously returned every EventType owned by the current user (`userId = currentUser`); the new condition restricts it to non-team event types only. Team event types are then expected to come from Part 2, which discovers them via an INNER JOIN on Membership. But a team event type whose `userId` is set to the current user while that user has no Membership row for the team falls through both branches: Part 1 excludes it (teamId is not null) and Part 2 excludes it (no Membership). The result is that such owned team event types silently disappear from the listing, breaking the event-types view for owners-without-membership.
The new eventDecoder builds each event's row from `getPhysicalColumnsSchema`, which drops every computed column, stored ones included. When the crud writer applies a replicated delete for a row the destination does not have, the table handler passes that row to `tombstoneUpdater.updateTombstone`. The tombstone updater's row.Deleter is built from `writeableColunms`, which keeps stored computed columns, and indexes the row by position. On a table with a stored computed column, every later column's datum is shifted. For example, on `(k INT PRIMARY KEY, c INT AS (k+1) STORED, v INT, INDEX (v))` the Deleter reads `v` at ordinal 2 of a 2-element row, and secondary-index encoding panics with index out of range. A stored computed column ahead of a primary-key column shifts the primary-key datum in the same way.
TopicRetriever fetches the embed/feed URL with `open(url).read` (Readability) and `open(SiteSetting.feed_polling_url)`. The only guard is `invalid_host?`, which pins the initial referer/embeddable_host; open-uri transparently follows HTTP redirects, so a whitelisted host returning a 3xx to an internal address (link-local 169.254.169.254, a private IP, or a localhost admin port) reaches it. This is a redirect-based SSRF that the host whitelist does not cover.
This PR renames the private storage download/delete route from a single-segment [fileName] dynamic parameter to a catch-all [...filePath], specifically so it can also serve the newly introduced /storage/{workspaceId}/private/surveys/{surveyId}/elements/{elementId}/{file} scoped upload paths (per the PR's own description: "Scope new private upload URLs under .../surveys/{surveyId}/elements/{elementId}/..."). Both the nested route shape and the underlying storage key scheme for element-scoped uploads are new in this diff. Routing these newly introduced, more sensitive per-response upload files through the SAME entry point -- still gated only by the pre-existing, role-blind hasUserWorkspaceAccess (see d1) -- exposes them to billing-role users for the first time. This is a diff-attributable widening of exposure, distinct from d1's own (pre-existing, unchanged) check logic: unlike d1, this defect is genuinely introduced by the diff and should not be excluded from headline scoring.
This change deletes the `github.com/scottlepp/go-duck/duck` dependency and points every SQL expression call at a new local `sql.DB` whose three methods each return `errors.New("not implemented")`. `parser.go` swaps `duck.NewInMemoryDB()` for `NewInMemoryDB()` and `sql_command.go` does the same in `Execute`, so `sql.TablesList` now always fails and `NewSQLCommand` returns `BadRequest("sql-invalid-sql")` for any non-empty query. The unchanged legacy path in `pkg/expr/nodes.go` reaches it with no gate: its `case TypeSQL:` calls `UnmarshalSQLCommand(rn)` and, unlike the `TypeThreshold` branch directly above, takes no `toggles` argument. Any saved TypeSQL expression evaluated without FlagExpressionParser therefore fails to build on every evaluation, where it previously ran. Independent of d1: d1 is the flag function returning false in both branches, and fixing it leaves this failure in place, because `NewSQLCommand` dies in `TablesList` before `Execute` is ever reached.
The informer transform `trim` calls `accessor.SetManagedFields(nil)` unconditionally on every resync, mutating the object that lives in the shared informer cache. Because that cached object is read concurrently by other informer consumers, the unconditional in-place mutation is a data race that can panic kube-controller-manager / scheduler. The fix guards it (`if accessor.GetManagedFields() != nil`) so the transform is idempotent and does not rewrite shared state when already trimmed.
In `prepareResources`, the branch that handles an already-prepared claim (`if claimInfo.isPrepared()`) does `return nil` instead of `continue`. Because this runs inside the `for ... range pod.Spec.ResourceClaims` loop, the first already-prepared claim short-circuits the whole loop and the pod's remaining ResourceClaims are never prepared. The fix changes `return nil` back to `continue`.
Continue requests are served from a cache snapshot without a freshness wait, so a lagging cache returns a stale, incomplete page. A continue request carries no explicit ResourceVersion (forbidden), so `Cacher.GetList` computes `listRV = 0` and `WaitUntilFreshAndList` does not block; the serve path then calls `listExactRV(key, continueKey, continueRV)` -> `snapshots.GetLessOrEqual(continueRV)`, which returns the greatest snapshot <= continueRV even when the cache has not reached continueRV, and labels the response `ResourceVersion = continueRV`. In an HA cluster a continue token minted by a fresh apiserver A and routed to an apiserver B whose watch cache lags continueRV yields an older snapshot's page mislabeled at continueRV, silently dropping objects created in (snapshotRV, continueRV].
The response-handling refactor builds the /_next/data JSON page response as Buffer.from(JSON.stringify(result.value.pageData)). RenderResult.isDynamic decides static-vs-dynamic via `typeof this.response !== 'string'`, so a Buffer is misclassified as a dynamic stream; sendRenderResult then skips Content-Length and ETag and falls back to Transfer-Encoding: chunked, breaking CDN-side compression for self-hosted Pages Router deploys. The fix deletes the Buffer.from wrapper. (Large-diff stress case: ~3k lines, 22 files.)
In app-page.ts the resume-render branch calls getFallbackRouteParams(pathname) where pathname (parsedUrl.pathname, interpolated in prepare()) is the resolved concrete path with no [param] segments, so getRouteRegex finds no dynamic keys and returns null; it should use normalizedSrcPage (the route pattern) as the sibling PPR-fallback call and the original base-server pathname (match.definition.pathname) did, breaking PPR fallback-shell param postponement for dynamic routes when renderFallbackShell is set in production.
In the app-route template's on-demand-revalidate path, responseGenerator correctly writes a real 404 response (res.statusCode = 404; res.end(...)) and returns null when isOnDemandRevalidate && revalidateOnlyGenerated && !previousCacheEntry. Back in handleResponse, because this route is ISR-eligible (isIsr is true -- it's determined solely by prerender-manifest membership, independent of the on-demand-revalidate flags, and on-demand revalidation is inherently an ISR-only feature), the `if (!isIsr) return null` short-circuit is skipped, and cacheEntry?.value?.kind !== CachedRouteKind.APP_ROUTE (true, since cacheEntry is null) throws an "Invariant: app-route received invalid cache entry" error -- even though a valid 404 HTTP response was already sent to the client. Because isIsr is true, the surrounding catch re-throws this spurious error rather than swallowing it, propagating it up through base-server onto an already-ended response.
With `trailingSlash: true`, the new handler templates (app-page.ts, app-route.ts, pages.ts) take `resolvedPathname` from the request URL, which base-server now rebuilds from the raw `initURL` and which still ends in a slash. None of them calls `removeTrailingSlash`, which base-server applied before its cache-key and prerender lookups. The build writes prerender-manifest keys without the slash, so every lookup misses. For app-page, a prerendered page on a `dynamicParams = false` route is taken to be unlisted and throws NoFallbackError (404), and the ISR cache key becomes `/blog/a/`, so the prebuilt output is never served.
The re-implemented Server Action reducer now rejects the action's promise with a redirect error for every redirect, external ones included, where it previously resolved them, and builds that error's URL with createHrefFromUrl, which keeps only the path and query, so an external URL loses its origin. Called from a form action or useTransition, React catches the handled error and the external navigation that handleExternalUrl staged (mpaNavigation) goes through. Called outside a React scope, such as a plain onClick, the rejection reaches the app router's unhandledrejection handler, which pushes the same-origin path; that navigation supersedes the external one, so the redirect to the external URL never happens.
The PR added API-key environment scoping to only the create and update integration routes. The sibling mutations removeIntegration, setIntegrationAsPrimary, and autoConfigureIntegration on the same controller were left unscoped, so an API key from one environment can delete, re-prioritize, or auto-configure integrations in another environment of the same org (cross-environment IDOR).
The change narrows shouldShowSyncColumns with `&& selectedConnector.supportsColumnSelection`, correct for column-selection but the same flag also gates the Sync-method, Sync-field, and Primary-key columns. supportsColumnSelection is false for all non-SQL sources (Stripe, Hubspot, REST), so those three controls silently disappeared for every non-SQL source during table setup.
A new usage-report query runs raw `FROM logs` through sync_execute() on the logs cluster. HogQL resolves its `logs` table to the physical `logs_distributed` table, and production's logs cluster has no table named `logs`: the `logs` Distributed table that migration 0214 creates exists only in local and test schemas, which is why the PR's test passes. In production the query fails, and since the new query runs unconditionally it aborts the whole usage-report run that feeds billing (reverted the next day in #60611).
In pkg/querier/postprocess.go the new prepareFillZeroArgsWithStep builds the fillZero function args as {req.Start, req.End, step} where step is computed in milliseconds (query.StepInterval.Duration.Milliseconds()) but req.Start/req.End are not guaranteed to be in milliseconds at runtime (callers may pass nanosecond-resolution timestamps). funcFillZero requires all three args in the same unit and loops from start to end by step appending one point per iteration; when start/end are nanoseconds and step is milliseconds the iteration count is ~10^6x too large, so the fill-zero path allocates an enormous slice of zero points and blows up memory / OOMs the query service.
medium 49/91 (53.8%)
valid_entries() uses a bare truthiness check (`if e`) but its docstring promises "the non-empty entries." This silently drops legitimate falsy-but-non-empty values too -- 0, 0.0, False, [], {} -- not just "" or None. Any caller passing counts, scores, or booleans loses valid entries with no error raised.
commit() gates the staged navigation on truthiness (`if (state.pendingMpaNavigation)`), so an empty-string url is indistinguishable from the `null` initial state and the redirect is silently skipped. Before the diff the reducer called navigate(action.url) directly with no gate, so navigate("") ran. `Action.url` is typed `string` with no non-empty constraint, so dispatch({ type: "redirect", url: "" }) type-checks at the public boundary. Same falsy-vs-absent collision as t1-py-filter-shifts-pairing d2, introduced here by the new staging step.
The diff adds `await prisma.workflowReminder.update(...)` inside the loop's catch block, which previously held only a `console.log` and so could not fail. Nothing wraps the loop: the handler's only try/catch is the inner one, and the `for` at line 55 closes with no surrounding handler, so a throw from that update escapes the loop and the handler, and `res.status(200).json(...)` is never reached. One reminder's DB failure now aborts the whole batch, where before each iteration was isolated. Reachable: Prisma's update raises P2025 when the row is gone, which this diff makes likelier by adding a deleteMany branch that can remove rows a concurrent cron run is processing. Independent of d2 and d3 -- d2 is the missing `method: SMS` filter on deleteMany, d3 is the locked-account misclassification, and fixing either leaves this failure path in place. Medium rather than high: the unreached reminders keep `scheduled: false` and fall inside the query's `scheduledDate <= now + 7 days` window, so the next cron run picks them up. The loss is fault isolation and a deferred batch, not dropped reminders, and it only reaches a user when a send time falls inside the gap before the next run.
Passing 80% as the dimensions can fail for animated GIFs when allow_animated_thumbnails is true, since the animated path uses gifsicle --resize-fit which expects WxH geometry, not a percentage; downsizing would then silently fail.
The new downsize loop tests `tempfile.size` and passes the same expression as the filesize argument to `Upload.create_for`, but the conversion ends in an image optimizer that atomically replaces the file. After the first pass the open Tempfile descriptor refers to an orphaned inode, so the reported size stops tracking the file on disk: the loop condition is frozen at the post-first-pass value and the upload is then rejected as too large by the validator even though the file has been shrunk well under the limit.
The filename language guesser reuses one `checked_tag` latch for both the hearing-impaired (`sdh`/`hi`/`cc`) and the newly added `forced` suffix, so only the last dot-separated suffix is ever tested as a tag. For a subtitle named `movie.en.sdh.forced.srt` the parser strips `forced`, sets the latch, and then reads `sdh` as the language, returning language "sdh" with the hearing-impaired flag unset. With the suffixes the other way round, `movie.en.forced.sdh.srt`, the six-letter `forced` fails the primary-subtag length check, so no language is found and the forced flag is lost. The wrong language reaches real tracks through subtitle autoload and sub-reload.
`toggleItem` declares `index: v.number()`, which accepts any float and NaN, and guards with `if (args.index < 0 || args.index >= checklist.length)`. Both comparisons are false for NaN, and 0.5 sits inside the range, so the guard passes, `checklist[args.index]` is `undefined`, and reading `.completed` off it throws an unhandled TypeError. Reachable from the public mutation API, which is what the validator exists to constrain.
Backup code validation is case-sensitive due to the use of indexOf(). This causes validation to fail if a user enters uppercase hex characters, as backup codes should be case-insensitive for a better user experience.
The diff converts the outer cancellation lookup from `find` to `filter` and loops over every calendar reference, but the recurring branch still resolves a single reference with `references.find((ref) => ref.type.includes('_calendar'))` and iterates only the organizer's credentials. For each remaining occurrence only the first reference is deleted and only with the organizer's credentials, so team members' calendar events survive the cancellation.
`sendAddGuestsEmails` takes no event-type metadata and unconditionally sends to the organizer, every team member and every attendee, while every other booking-lifecycle sender in the same file gates on the helpers that read `disableStandardEmails.all.host` and `.attendee`. The handler already loads the event type, so the metadata is in hand and simply not passed, and an organizer who disabled standard emails still has them sent.
The new immediateDelete branch of deleteScheduledEmailReminder cancels the scheduled email at SendGrid on the spot, and three new call sites use it (rescheduling in handleNewBooking, workflow and workflow-step deletion in workflows.tsx). Each such cancellation stays pending in SendGrid's scheduled_sends until the email's send time, up to 72h ahead, and SendGrid allows only 100 pending cancellations: the limit this PR's deferred, cron-driven cancellation exists to stay under. Under steady rescheduling the immediate cancellations fill it, after which cancellations are rejected (and only logged), both the immediate ones and the cron's deferred ones, so reminders for rescheduled and cancelled bookings are sent anyway.
Statement IDs are built with `h := fnv.New128()`; the stdlib hash/fnv constructor heap-allocates a hash object on every statement, and the ID is constructed even when not required. On hot SQL paths this is a measurable allocation/throughput regression (the fix's microbenchmarks show kv95 +3.42%). The fix uses a lightweight value-type FNV and only builds the ID when needed. (Large-diff stress case: ~2.8k lines, 14 files.)
`resetAndMaybeDumpStats` copies and re-makes `a.stmts` but the diff's new per-fingerprint `a.txns` map is neither transferred to the copy nor cleared. Transaction statistics therefore survive every reset, are never handed to the reported-stats sink, and accumulate one entry per distinct transaction fingerprint for the lifetime of the node.
The new image-set loader offers a "Pad" resize option whose branch is identical to "Stretch": it calls the same full resize to the target width and height, with no aspect-preserving thumbnail and no border fill. A user who loads a folder of differently sized images and picks "Pad" to keep aspect ratio gets every image whose size differs from the first one non-uniformly squashed, silently corrupting the training data, with nothing reporting that the chosen option behaved the same as "Stretch".
NoMethodError before_validation in EmbeddableHost
The new plural-ID hydration branch in `_hydrateEmbedded` (added alongside the existing singular path) maps a list of ids through `_lookupSubType` and assigns the result unconditionally: `obj[self.pluralize(subType)] = hydrated || []`. `_lookupSubType` returns `undefined` for an id whose root collection or specific id isn't found; since Array.prototype.map always returns an array, `hydrated` is always truthy and the `|| []` fallback never fires, so the resulting array can contain literal `undefined` entries (e.g. [ModelObj, undefined, ModelObj]). This is the reverse of the existing singular path, which correctly guards with `if (hydrated)` before assigning.
`ZUploadPrivateFileRequest` gains `elementId` as a required string with no `.optional()` and no default, and its single consumer returns 400 on parse failure before destructuring the field into the signed-URL path. The published contract is not updated: the OpenAPI reference still documents the endpoint as requiring only surveyId, fileName and fileType, and the diff does not touch it.
`isScopedPrivateUploadUrl` rejects anything that is not exactly the new eight-segment shape (`if (segments?.length !== 8) return false`), and `validateClientFileUploads` fails on that. Legacy private upload URLs are four segments, so a response created before the deploy can never be updated afterwards. The same diff's `parseStorageFileUrl` is deliberately tolerant, so the delete path stays backward compatible while the validate path does not.
The new permission-denial cache key concatenates namespace, user, action, name and parent with underscores, but underscores are legal in Grafana UIDs, so distinct tuples collide -- a resource named `alerts_prod` in folder `team` produces the same key as `alerts` in folder `prod_team`. A denial recorded for one then short-circuits the check for the other, returning not-allowed without evaluating permissions for the cache lifetime.
`useAllAlertRuleAbilities` is rewritten to delegate to an implementation that hardcodes `const isFederated = false`, deleting the real `isFederatedRuleGroup(rule.group)` check that fed `immutableRule`. Federated Mimir rules are therefore treated as editable: the rule list renders an Edit button that opens the rule editor, where pre-diff the ability was NotSupported and no button appeared.
`TestNewClaimInfoFromClaim` and `TestNewClaimInfoFromState` assert with an inverted condition: `if reflect.DeepEqual(result, test.expectedResult) { t.Errorf(...) }`. That reports a failure only when the result MATCHES the expectation, so the tests never validate the constructor and pass vacuously (and `expectedResult` is left nil). The fix inverts the check to `if !reflect.DeepEqual(...)`.
The claimInfo-cache tests seed their "item in cache" fixtures under the key `claimName + namespace`, but the cache itself keys entries on `namespace + "/" + claimName`. The mismatched key means the seeded entry is never found, so the `get`/`delete`/`contains` tests pass vacuously without exercising the real lookup. The fix keys the fixtures on `namespace + "/" + claimName` to match the cache.
The cacher delegator's `GetList` adds an unconditional `if errors.IsResourceExpired(err) { return c.storage.GetList(...) }` fallback to etcd. When the cache snapshot is nil the cacher returns `ResourceExpired`, so consistent paginated LISTs silently fall back to etcd instead of being served from cache, defeating the feature and adding etcd load. The fix gates that fallback behind the cache-snapshot feature flag.
The diff removes the fail-fast `IllegalStateException` that rejected multiple crypto providers on the classpath, replacing it with an order-based sort, a debug log and `foundProviders.get(0)`. All three real providers return the same order value, and `Stream.sorted` is stable, so a tie is resolved by ServiceLoader enumeration order: on a deployment carrying both the default and the FIPS provider, which one is selected depends on classpath ordering rather than configuration.
Both group list endpoints drop the hoisted global permission check (`boolean canViewGlobal = groupsEvaluator.canView()`) and filter with a per-group `groupsEvaluator::canView`. Under fine-grained admin permissions v2 that per-group call falls through to a resource lookup and a full uncached policy evaluation, so one evaluation becomes one per group; the subgroup endpoint is worse because it fetches subgroups unbounded and paginates only after filtering.
In verifySafeHtml the prefix length `start` and suffix length `end` are computed independently with no `start+end <= value.length()` guard, so when the OWASP sanitizer balances mis-nested allowed tags (e.g. `<p><b>x</p>` → `<p><b>x</b></p>`) the overlapping prefix/suffix make `value.substring(start, value.length()-end)` have beginIndex > endIndex, throwing StringIndexOutOfBoundsException exactly on the illegal-HTML case it should report.
The client-credentials grant builds its token through `tokenManager.responseBuilder(...).generateAccessToken()` directly, bypassing the shared response path where the diff sets `Constants.GRANT_TYPE` on the client session context. `initToken` then reads that attribute, finds it null and substitutes the unknown marker, so every client-credentials token id encodes `na` rather than the shortcut the diff registers for this grant. Every other direct-responseBuilder path in the PR was updated; this one was missed.
The textarea XML schema is changed to declare the placeholder property as `placeholder_text`, but the textarea XML parser, which the change does not touch, still matches only the attribute name `placeholder`. XML written against the updated schema, such as `<lv_textarea placeholder_text="Type here"/>`, matches no branch in the parser's attribute chain, so `lv_textarea_set_placeholder_text` is never called. The attribute loop has no unknown-attribute warning, so the placeholder is dropped silently.
`grid_update` gains an early return when the grid calculation fails, but the calculation has already allocated its row arrays by then and the early return skips the free routine. A grid container that has a row descriptor but no column descriptor, on itself or its parent, gets `c->y` and `c->h` allocated in the row pass and then fails the column pass, leaking both arrays on every layout refresh. Calling the existing free routine at that point is not by itself a safe fix, because the struct is not zeroed on every failure path.
`SourceUtils.findMatchingChild` iterates a folder's children and returns the first name match without excluding directories (no `isFolder()` / file-vs-folder check). A directory whose name equals the class name (e.g. a package dir `Test/` next to `Test.java`) is returned as the "source file", so go-to-source resolves to a folder instead of the file. The fix skips folders when matching.
The image-optimizer move to response-cache dropped the maxAge argument to sendResponse and hardcoded the cached-image header to `public, max-age=0, must-revalidate` instead of `max-age=${maxAge}`. The computed upstream/minimumCacheTTL maxAge is no longer propagated, so every optimized image returns max-age=0 and CDNs/browsers in front of a single instance stop caching, inflating origin load. (Large-diff stress case: ~3.6k lines, 15 files.)
In imageOptimizer's internal-request path, `if (!mockRes.statusCode)` can never be true for any real HTTP status code (`mockRes.statusCode` starts at 200 and is only ever set to other truthy numbers like 404/500 by `handleRequest`), so the intended check for a failed internal response never fires. The old code additionally forwarded the upstream status via `res.statusCode = mockRes.statusCode`; this diff removes that forwarding entirely, so an internal 404/500 is masked behind an eventual 200 (until a secondary content-type check happens to catch it).
`unstable_revalidate`'s new try/catch around the revalidation fetch discards the real error entirely: both a network failure and a non-OK HTTP response from the revalidation endpoint are collapsed into an identical, opaque `Failed to revalidate ${urlPath}` error with no status code, so callers can no longer distinguish a network outage from a 404/500 returned by the endpoint being revalidated.
The pages template sets `isIsrFallback` for an ungenerated path of a `fallback: true` route and clears it only for bots, minimal mode or an existing cache entry, never for on-demand revalidation. Base-server forced a blocking render when `isOnDemandRevalidate` was set. So `res.revalidate('/posts/new')` for a path not yet generated now returns the build-time fallback shell with its cache control deleted: nothing is stored, yet the response carries `x-nextjs-cache: REVALIDATED`, so the revalidate call reports success without generating the page.
The app-page template adds an early `if (isSSG && prerenderInfo?.fallback === false && !isPrerendered) throw new NoFallbackError()` that runs before draft mode or minimal mode is considered. The base-server check it replaces skipped preview/draft mode and minimal mode, and the sibling pages and app-route templates keep a `!isDraftMode` guard. A draft-mode request for a path of a `dynamicParams = false` app page that was not prerendered now returns 404 instead of rendering on demand, which breaks CMS preview of unpublished pages.
OAuth state uses pipeline.signature (static) instead of a per-request random value
In applyFormulas (pkg/querier/postprocess.go), the new RequestTypeScalar branch calls applySeriesLimit on the result of processScalarFormula, but that result's Value is a *qbtypes.ScalarData while applySeriesLimit type-asserts result.Value.(*qbtypes.TimeSeriesData) and returns the result unchanged when the assertion fails. So for scalar/formula query results the call is effectively dead code: the configured order-by and limit on the formula are silently ignored, and scalar formula results come back unordered with no limit applied.
The new `HasOrderSpecified()` type-switches over the trace, log, metric and formula query types and omits `QueryBuilderTraceOperator`, which carries its own `Order` field and is a first-class member of the same pipeline. `applyDefaultSort` is therefore true for a trace-operator query that did specify an order, and the scalar formatter re-sorts by the first aggregation -- the descending re-sort this PR exists to suppress.
In VisitComparison's IN-clause branch, `case []any: values = varValues` passes an empty slice straight through when a variable resolves to []any{}. condition_builder.go's FilterOperatorIn handler then builds conditions := []string{} from an empty values, and sb.Or(conditions...) with zero arguments returns an empty string (confirmed in the vendored huandu/go-sqlbuilder@v1.35.0 source: Or returns "" when len(orExpr) == 0 after filtering). The generated WHERE-clause fragment for that condition vanishes rather than encoding "no rows match", so a filter meant to exclude everything silently matches all rows instead.
chSQLQuery.renderVars substitutes variable values into the raw ClickHouse query string via strings.Replace BEFORE parsing that string as a Go text/template (tmpl.Parse(query) / tmpl.Execute). If a variable's own VALUE contains the Go template delimiters {{/}}, the substituted text is then re-interpreted as a live template action in the second stage -- e.g. a variable value of "{{.SIGNOZ_START_TIME}}" gets replaced with the numeric start timestamp rather than being treated as literal text, silently changing the rendered query; a malformed template fragment (e.g. "{{.") causes template.Parse to fail, surfacing as an opaque HTTP 500.
parseFieldKeyRequest renames the field-key search parameter from ?name to ?searchText (r.URL.Query().Get("name") -> r.URL.Query().Get("searchText")). parseFieldValueRequest calls parseFieldKeyRequest internally (now reading ?searchText) and separately reads ?name for a different purpose (keySelector.Name, overriding what the key-request set). Any existing caller using GET /api/v1/fields?name=service_name to filter the field-key list gets back all keys instead of a filtered set -- the ?name parameter is simply ignored for that endpoint, a breaking API change with no version bump.
rewriteExpression replaces all quoted string literals in the HAVING expression with __QUOTED_N__ placeholders BEFORE matching column-map keys against it. A key like countIf(level='error') (itself containing a quoted literal) is turned into a regex built from its raw, unprotected form, so it can never match the already-placeholder-substituted expression -- e.g. a HAVING clause countIf(level='error') > 10 reads as countIf(level=__QUOTED_0__) > 10 after quote-protection, and the \bcountIf\(level='error'\) pattern silently fails to match, so the rewrite (and the __result_N substitution downstream code depends on) is silently skipped.
low 16/32 (50.0%)
Wrapping `.small-action` in `@include flexbox()` (topic-post.scss) silently breaks the layout of its children. `.small-action` still contains the pre-existing `button { float: right }`, `.topic-avatar { float: left }`, and `clear: both`, but floats are ignored on flex items, so the action button is no longer right-aligned and the avatar/desc layout collapses. This is the flexbox side-effect that forced the upstream revert.
The reader thread isn’t waited for; flipping deletedAll to true and asserting immediately can race and miss exceptions added just after the flag change, making this test flaky.
The new checklist mutations write no `activityLog` entry, while every other task-mutating operation does: `create`, `update` and `remove` in convex/tasks.ts each call `ctx.runMutation(internal.activity.log, ...)`. A task's checklist can therefore be changed with no record, leaving the activity history incomplete for that class of edit.
Because backupCodes are decrypted and mutated in memory before being written back, two concurrent login requests using the same backupCode could both pass this check and update, so a single backup code may effectively be accepted more than once if used concurrently, weakening the intended one-time-use semantics.
uniqueGuests filters out existing attendees and blacklisted emails but does not deduplicate duplicates within the input; createMany can insert duplicate attendee rows if the client submits repeated emails.
logic: macOS-specific sed syntax with empty string after -i flag will fail on Linux systems
The update and destroy methods in Admin::EmbeddableHostsController do not validate the existence of the EmbeddableHost record retrieved by ID. If EmbeddableHost.where(id: params[:id]).first returns nil (i.e., the host does not exist), attempting to call methods on the nil object (e.g., save_host or destroy) will result in a NoMethodError.
The new `EmbeddableHost` model's format validation explicitly accepts a port (`(:[0-9]{1,5})?`), and `before_validation` strips only the scheme and path, so a host entered as `http://example.com:3000` or `example.com:3000` is stored as `example.com:3000`. `record_for_host` compares the port-less `URI#host` of the referer against that stored value, so it can never match, and embedding from that site is silently refused although the admin UI accepted the host.
The postMessage origin check uses reversed substring matching (`discourseUrl.indexOf(e.origin) === -1`), accepting any origin that is a substring of the configured Discourse URL rather than requiring an exact origin match; impact is limited to letting a non-Discourse frame resize the embed iframe.
The test comment says the cached permissions 'allow access', but the map stores false for dashboards:uid:dash1, so checkPermission will still treat this scope as not allowed.
Cleanup reference uses incorrect alias - should be 'idp-alias-' + i instead of 'alias'.
Dead code exists where ASN1Encoder instances are created and written to, but their results are immediately discarded. The actual encoding is performed by new ASN1Encoder instances created in the subsequent return statement, rendering the earlier operations useless.
The app-route template's outer catch now calls `routeModule.onRequestError(req, err, {...})` without the fourth `routerServerContext` argument that every other call site in this diff passes. `RouteModule.onRequestError` therefore falls back to a bare `console.error(err)` instead of `routerServerContext.logErrorWithOriginalStack`, so a server started with `quiet: true` now prints route-handler errors, a normal server loses the standard error prefix, and in dev the original-stack logger is skipped.
The app-page template's responseGenerator copies base-server's static-shell-debugging short-circuit, which returns a cache entry of `kind: CachedRouteKind.PAGES`. The template's own handleResponse then throws "Invariant app-page handler received invalid cache entry PAGES" for any kind other than APP_PAGE. Base-server served that entry through its generic branch as an empty HTML response, so a static-shell debugging request now fails with the invariant error.
The span bar position is computed with a CSS clamp: `left: clamp(0%, ${toPercent(bounds.left || 0)}, calc(100% - 1px))`. clamp floors the value at 0%, but when the view is zoomed via the minimap a span that starts before the visible window has a legitimately negative left; flooring it to 0% mis-positions the bar. The fix uses min(...) (no lower bound) so negative offsets render correctly.
With upsampling applied, events-stats sends the literal column `upsampled_count() as count` to the query builder. When the client also sets transformAliasToInputFormat=1, the builder's process_results renames the result key to that full input string, while the serializer looks up `count()` (resolve_axis_column returns the raw y-axis). `r.get(column, 0)` then finds nothing, so every bucket of the time series comes back as 0.

By diff size — compare every bot

Keeps pace with the field

The gap moves -1 pts from small to large, so it drops off about as much as the other bots do as PRs grow.

Diff sizeCasesBugs caughtCoverageOther bots, same PRsvs othersFalse-alarms
small ≤100 lines 54 50/64 82% 87% -5 pts 1%
medium 101–500 lines 40 52/74 71% 73% -2 pts 6%
large >500 lines 33 48/98 54% 61% -6 pts 2%

Every bot catches less as PRs grow, so a falling coverage number is expected. The question is whether this bot falls more or less than the others. vs others is its coverage minus what the other bots caught on the exact same PRs. The label compares that gap on small PRs with the gap on large ones; it takes a 10-point move to count. Coverage is severity-weighted: a critical bug counts 8×, a low one 1×.

Review time

Median 2.1 min and 90th percentile 4.2 min over 127 reviews.

Diff sizeReviewsMedian90th percentile
small ≤100 lines541.2 min2.5 min
medium 101–500 lines402.9 min4.3 min
large >500 lines333.1 min6.3 min

Timed from the start of the review to its end, run on our machine two at a time, so it has no queue to wait in. Times measured this way and a hosted bot's are not strictly comparable. See methodology.

Trajectory — coverage over time

RunCoverageValidityCases
2026-11-08-s181.0%95.8%63
2026-11-10-s160.0%97.5%64

Cases reviewed

Authored · Tier 1 · found 37/39 · 36 cases

CaseFoundFindingsFalse-alarms
A new required TRACKER_GEOCODER_URL setting is not added to the Helm chart, so every pod fails at startup 1/1 2 0
A new required TRACKER_GEOCODER_URL setting is not added to the Helm chart, so every pod fails at startup 1/1 2 0
Binary-sink migration missed an unchanged Serializer implementer (CsvSerializer still returns str) 1/1 2 0
Binding the tenant scope with `let _ =` drops the guard at once, so the digest reads every tenant's rows 1/1 2 0
Day-bucketing the keyset filter in the session timezone diverges from the UTC-pinned cursor and empties page 2 1/1 2 0
Environment scoping added to create/update but not the sibling delete leaves a cross-env IDOR 2/2 4 0
Filtering empty entries silently misaligns audit's positional entry/timestamp pairing 1/2 2 0
Handlers are now built once per context instead of per event, so the PayoutFees the fee schedule keeps for each payout.paid handler, which charges each seller once, stops charging the payout fee after a seller's first payout 1/1 2 0
Handlers are now built once per context instead of per event, so the PayoutFees the fee schedule keeps for each payout.paid handler, which charges each seller once, stops charging the payout fee after a seller's first payout 1/1 2 0
Lowercasing tags silently breaks the case-sensitive admin check in access.py 1/1 2 0
Moving the Server Action redirect into the render commit drops it on the unchanged non-React result path 1/2 3 1
Narrowing a shared visibility gate for one control silently hides two unrelated controls 1/1 2 0
Rejecting a zero throttle interval silently stops an unthrottled heartbeat that must always fire 1/1 2 0
Reordering Job's fields silently re-ranks the unchanged scheduler's heap by name instead of priority 1/1 2 0
Reusing a scratch buffer for end keys corrupts every recorded span via the retaining writer 1/1 2 0
Routing Amex to the legacy gateway breaks payments via an unchanged capability the diff can't see 1/1 2 0
Sorting the roster silently misaligns payroll's positional name/amount pairing 1/1 2 0
Stripping the trailing slash silently malforms URLs built by the unchanged helper 1/1 2 0
Switching encode() to chunks_exact silently discards the partial final frame of every batch 1/1 2 0
Switching flusher workers to the spawn context silently disables the reaper's isinstance-gated kill 1/1 2 0
The cached shipment payload changes shape without bumping CACHE_VERSION, so old entries are read as current 1/1 2 0
The cached shipment payload changes shape without bumping CACHE_VERSION, so old entries are read as current 1/1 2 0
The location record gains a field but the TypeScript client decoder keeps the old record layout 1/1 2 0
The location record gains a field but the TypeScript client decoder keeps the old record layout 1/1 3 0
check now sees each family's canonical values, and for an EDI line canonical() sets the quantity in units through units(), so Pinecrest's cap on the quantity as ordered rejects every case line over 150 units 1/1 2 0
check now sees each family's canonical values, and for an EDI line canonical() sets the quantity in units through units(), so Pinecrest's cap on the quantity as ordered rejects every case line over 150 units 1/1 2 0
load_flags() returns None for empty config, breaking the membership check in gate.py 1/1 2 0
position_of() not-found sentinel changed None -> -1, breaking router's `is None` guard 1/1 2 0
transform() returning nothing now drops the event, and an unchanged handler's transform still returns nothing, dropping every dispute 1/1 2 0
transform() returning nothing now drops the event, and an unchanged handler's transform still returns nothing, dropping every dispute 1/1 2 0
transform() returning nothing now drops the event, and the dispute handler's transform returns noteMissing(), which returns nothing, dropping every dispute 1/1 1 0
transform() returning nothing now drops the event, and the dispute handler's transform returns noteMissing(), which returns nothing, dropping every dispute 1/1 2 0
validate() now skips on a falsy return, and an unchanged handler's validate still returns None, dropping every refund 1/1 2 0
validate() now skips on a falsy return, and an unchanged handler's validate still returns None, dropping every refund 1/1 2 0
validate() now skips on a falsy return, and the refund handler's validate returns note_missing(), which returns the optional fields it found missing: an empty list for every refund that has a reason 1/1 3 1
validate() now skips on a falsy return, and the refund handler's validate returns note_missing(), which returns the optional fields it found missing: an empty list for every refund that has a reason 1/1 4 2

Cal.com · Tier 2 · found 21/36 · 11 cases

CaseFoundFindingsFalse-alarms
Add guest management functionality to existing bookings 3/5 7 1
Advanced date override handling and timezone compatibility improvements 3/4 7 1
Async import of the appStore packages 1/1 1 0
Comprehensive workflow reminder management for booking lifecycle events 2/3 5 0
OAuth credential sync and app integration enhancements 7/7 14 1
SMS workflow reminder retry count tracking 0/3 0 0
feat: 2fa backup codes 0/3 2 0
feat: `Troubleshooter` atom 0/1 1 0
feat: add calendar cache status and actions (#22532) 0/1 0 0
fix: handle collective multiple host on destinationCalendar 5/7 12 0
fix: instant booking location lookup 0/1 4 0

CockroachDB · Tier 2 · found 7/11 · 5 cases

CaseFoundFindingsFalse-alarms
Backup manifest EndKey stored without Clone is corrupted by a caller's scratch-buffer reuse 2/3 4 0
Crud writer feeds tombstone updates a row without stored computed columns, panicking the Deleter 0/1 2 0
Per-statement fnv.New128() allocation is a hot-path throughput regression 2/4 4 0
Tombstone updater re-leases its descriptor on every call and reports failed updates as success 2/2 5 0
Treating min_checkpoint_frequency=0 as 'disabled' stalls the changefeed highwater 1/1 3 0

ComfyUI · Tier 2 · found 0/1 · 1 cases

CaseFoundFindingsFalse-alarms
Add LoRA trainer nodes and image-set loaders 0/1 13 0

Deno · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
fix(npm): handle deno run/install of npm package with only directories.bin 1/1 5 0

Discourse · Tier 2 · found 14/23 · 7 cases

CaseFoundFindingsFalse-alarms
Add comprehensive email validation for blocked users 1/1 4 0
Enhance embed URL handling and validation system 3/5 8 0
FEATURE: Can edit category/host relationships for embedding 4/8 4 0
FEATURE: automatically downsize large images 2/4 4 0
FEATURE: per-topic unsubscribe option in emails 2/2 4 0
FIX: proper handling of group memberships 2/2 6 0
Optimize header layout performance with flexbox mixins 0/1 2 0

Django · Tier 2 · found 2/2 · 1 cases

CaseFoundFindingsFalse-alarms
Fixed #36273 -- Moved Index system checks from Model to Index.check(). 2/2 6 0

Formbricks · Tier 2 · found 1/4 · 2 cases

CaseFoundFindingsFalse-alarms
Add response-pipeline webhook delivery job 1/1 3 0
Storage auth session path uses a role-blind access check, letting billing-role users escalate 0/3 0 0

Grafana · Tier 2 · found 14/19 · 9 cases

CaseFoundFindingsFalse-alarms
Advanced SQL Analytics Framework 1/2 2 0
Anonymous: Add configurable device limit 2/2 3 0
AuthZService: improve authz caching 0/2 1 0
DashboardDS: Fix Mixed panels not updating on time-range change with stale upstreams 1/1 2 0
Database Performance Optimizations 2/2 4 0
Dual Storage Architecture 4/4 7 0
Frontend Asset Optimization 1/1 1 0
Notification Rule Processing Engine 2/3 6 0
Unified Storage Performance Optimizations 1/2 1 0

Keycloak · Tier 2 · found 7/14 · 9 cases

CaseFoundFindingsFalse-alarms
Add AuthzClientCryptoProvider for authorization client cryptographic operations 0/2 0 0
Add Client resource type and scopes to authorization schema 1/1 3 1
Add Groups resource type and scopes to authorization schema 2/3 4 0
Add HTML sanitizer for translated message resources 0/1 3 0
Add caching support for IdentityProviderStorageProvider.getForLogin operations 0/1 1 0
Add rolling-updates feature flag and compatibility framework trap 0 0
Fix concurrent group access to prevent NullPointerException 0/1 0 0
Fixing Re-authentication with passkeys 2/2 4 0
Implement access token context encoding framework 2/3 4 0

Kubernetes · Tier 2 · found 1/8 · 4 cases

CaseFoundFindingsFalse-alarms
Reduce cache locking duration when the DaemonSet controller fetches pods 0/1 0 0
Serve LISTs with exact ResourceVersion and continuations from the cache 1/3 2 0
Trim managedFields in the controller-manager and scheduler informer transforms 0/1 0 0
kubelet DRA: update claimInfo cache locking and checkpoint semantics 0/3 2 0

LVGL · Tier 2 · found 1/3 · 1 cases

CaseFoundFindingsFalse-alarms
xml: sync the widget schemas with the runtime parsers 1/3 7 0

mpv · Tier 2 · found 0/1 · 1 cases

CaseFoundFindingsFalse-alarms
player: detect forced subtitle tracks from the filename 0/1 2 0

n8n · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
fix(editor): Load credentials when opening node credential picker 1/1 2 0

NetBeans · Tier 2 · found 1/2 · 2 cases

CaseFoundFindingsFalse-alarms
Extract the source file name from the .class and use it to locate the source 0/1 4 0
LSP: do not compute text edits in source actions on resolve 1/1 1 0

Next.js · Tier 2 · found 2/15 · 4 cases

CaseFoundFindingsFalse-alarms
Image optimizer hardcodes max-age=0, discarding the upstream cache TTL 1/4 2 0
Passing nextConfig: undefined also disables basePath stripping, corrupting router.query 0/1 0 0
Server Action external redirect is dropped when invoked outside a React scope 0/1 1 0
Wrapping the data response in a Buffer misclassifies it as dynamic, dropping Content-Length and ETag 1/9 6 0

Novu · Tier 2 · found 0/1 · 1 cases

CaseFoundFindingsFalse-alarms
Environment scoping added to create/update integration routes but not the sibling mutations 0/1 0 0

OpenCV · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
videoio: add IStreamReader support to the Java bindings 1/1 3 0

PostHog · Tier 2 · found 2/4 · 6 cases

CaseFoundFindingsFalse-alarms
Email-queue routing parks workflow waits on a queue the subscription matcher never searches 1/1 4 0
Hardcoded queue_name='hogflow' filter never finds email-routed parked waits trap 1 1
Narrowing a shared visibility flag hides sync-method/field/primary-key columns for non-SQL sources 0/1 2 0
Raw query uses the HogQL table alias 'logs' instead of the physical 'logs_distributed' 0/1 0 0
Timezone-unpinned toStartOfDay vs UTC-pinned date constants empties keyset page 2 trap 3 0
feat(sig): custom agents 1/1 2 0

Redis Client · Tier 2 · found 2/2 · 1 cases

CaseFoundFindingsFalse-alarms
Implement Write Barriers for HiredisConnection 2/2 3 0

Sentry · Tier 2 · found 19/23 · 10 cases

CaseFoundFindingsFalse-alarms
Enhanced Pagination Performance for High-Volume Audit Logs 3/4 7 1
GitHub OAuth Security Enhancement 1/2 2 0
GitLab integration search returns full project paths 2/2 4 0
Optimize spans buffer insertion with eviction during insert 3/3 9 0
Span Buffer Multiprocess Enhancement with Health Monitoring 2/2 3 0
Span tree minimap and secondary panel 1/2 3 0
feat(ecosystem): Implement cross-system issue synchronization 1/1 2 1
feat(upsampling) - Support upsampled error count with performance optimizations 3/4 7 1
feat(uptime): Add ability to use queues to manage parallelism 2/2 6 0
feat(workflow_engine): Add in hook for producing occurrences from the stateful detector 1/1 2 0

SigNoz · Tier 2 · found 4/11 · 2 cases

CaseFoundFindingsFalse-alarms
chore: recognize variable in expression 4/9 7 0
fix: do not sort in descending locally if the other is explicitly specified 0/2 0 0

TaskFlow (Convex) · Tier 2 · found 11/13 · 10 cases

CaseFoundFindingsFalse-alarms
.collect() Just to Count (TaskFlow PR #6) 1/1 2 0
.filter() vs Index (TaskFlow PR #2) 1/1 2 0
Authorization Bypass (TaskFlow PR #10) 2/2 3 0
Exposed Internals (TaskFlow PR #4) 1/1 3 0
Missing Aggregate Update (TaskFlow PR #8) 1/1 2 0
Missing Auth Check (TaskFlow PR #3) 1/1 2 0
Nested Lookups (TaskFlow PR #1) trap 0 0
OCC Conflict on Hot Path (TaskFlow PR #9) 1/1 3 0
Unbounded .collect() (TaskFlow PR #5) 1/1 2 0
Unbounded Array in Document (TaskFlow PR #7) 2/4 2 0

Tauri · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
fix(core): Correctly detect Android Tauri configuration file, closes #7785 1/1 4 0