Prevents default browser shortcuts from modifying the file content locally.
This fixes a bug where we would apply a phrase boost if a content: filter was specified with keyword search enabled. This led to inconsistent behavior (regexp vs keyword search) and it also rendered the content: filter ineffective, because we ran a general text search instead of a just a content search.
Fixes a bug where hovers were not triggered for less mainstream languages like F#,
Standard ML, Visual Basic, Pkl, Hack, MATLAB etc.
Introduces new limits for auto-indexing inference to reduce the risk of continuously growing auto-indexing queues.
- The number of jobs spawned per round of auto-indexing inference per repo is capped (default: 100) to reduce risk of clogging of auto-indexing queues. Excess jobs will be discarded.
- The number of paths inspected for a single round of auto-indexing inference per repo is capped (default: 500) to reduce risk of timeouts. Excess paths will be discarded.
Fixes handling of SCIP uploads when the hash passed to the -commit flag of src-cli corresponds to the hash of an annotated tag instead of the hash of a commit. Previously, these uploads were not accessible for code navigation.
Fixes a bug where the retention tab for precise indexes would show
a nil pointer exception instead of retention information.
fix(batches): enable request splitting by default
fix(batches): handle spec being nil for suffix salt
fix(batches): enable GQL request splitting via BATCH_CHANGES_REQUEST_SPLITTING
fix(batches): display "Deleted Namespace" instead of throwing an error
fix(code-monitor): fail monitors with missing/unverified primary email address
Added token usage information to .api/llm/chat/completions
Fixes a bug where logs and traces were sometimes missing key-value pairs recorded alongside errors.
The documentation for gitserver's ReadDir method has been clarified to reflect that the return iterator's Name() method returns the full path of the file, as opposed to just the basename.
The documentation for the "exclude" section in the github code host connection schema has been clarified to explain that each block is OR'd together, and the expressions within each block are AND'd together.