issues  

Messages by Thread

• • Re: [I] Should we use a SparseFixedBitSet when deletes are sparse? [lucene] via GitHub
  • Re: [I] Should we use a SparseFixedBitSet when deletes are sparse? [lucene] via GitHub
  • Re: [I] Should we use a SparseFixedBitSet when deletes are sparse? [lucene] via GitHub
  • Re: [I] Should we use a SparseFixedBitSet when deletes are sparse? [lucene] via GitHub
  • Re: [I] Should we use a SparseFixedBitSet when deletes are sparse? [lucene] via GitHub
  • Re: [I] Should we use a SparseFixedBitSet when deletes are sparse? [lucene] via GitHub
• [PR] Failing workflow instead of comment on missing changelog entry [lucene] via GitHub
  • Re: [PR] Failing workflow instead of comment on missing changelog entry [lucene] via GitHub
  • Re: [PR] Failing workflow instead of comment on missing changelog entry [lucene] via GitHub
  • Re: [PR] Failing workflow instead of comment on missing changelog entry [lucene] via GitHub
  • Re: [PR] Failing workflow instead of comment on missing changelog entry [lucene] via GitHub
  • Re: [PR] Failing workflow instead of comment on missing changelog entry [lucene] via GitHub
  • Re: [PR] Failing workflow instead of comment on missing changelog entry [lucene] via GitHub
  • Re: [PR] Failing workflow instead of comment on missing changelog entry [lucene] via GitHub
• Re: [I] Incorrect use of fsync [lucene] via GitHub
  • Re: [I] Incorrect use of fsync [lucene] via GitHub
  • Re: [I] Incorrect use of fsync [lucene] via GitHub
• [I] Lucene104ScalarQuantizedVectorFormat returns different docs and scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different docs and scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different docs and scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
  • Re: [I] Lucene104ScalarQuantizedVectorFormat returns different scores after merging [lucene] via GitHub
• Re: [I] Allow skip_factor to be set dynamically within QueryCache [lucene] via GitHub
• [PR] deps(java): bump com.google.errorprone:error_prone_core from 2.42.0 to 2.43.0 [lucene] via GitHub
  • Re: [PR] deps(java): bump com.google.errorprone:error_prone_core from 2.42.0 to 2.43.0 [lucene] via GitHub
  • Re: [PR] deps(java): bump com.google.errorprone:error_prone_core from 2.42.0 to 2.43.0 [lucene] via GitHub
  • Re: [PR] deps(java): bump com.google.errorprone:error_prone_core from 2.42.0 to 2.43.0 [lucene] via GitHub
• [I] Improve round trip conversion of ValueSource <-> DoublesValueSource [lucene] via GitHub
  • Re: [I] Improve round trip conversion of ValueSource <-> DoublesValueSource [lucene] via GitHub
  • Re: [I] Improve round trip conversion of ValueSource <-> DoublesValueSource [lucene] via GitHub
• [I] Check for changelog entry is bit aggressive [lucene] via GitHub
  • Re: [I] Check for changelog entry is bit aggressive [lucene] via GitHub
  • Re: [I] Check for changelog entry is bit aggressive [lucene] via GitHub
• [PR] add .envrc to the gitignore [lucene] via GitHub
  • Re: [PR] add .envrc to gitignore [lucene] via GitHub
  • Re: [PR] add .envrc to gitignore [lucene] via GitHub
  • Re: [PR] add .envrc to gitignore [lucene] via GitHub
  • Re: [PR] add .envrc to gitignore [lucene] via GitHub
  • Re: [PR] add .envrc to gitignore [lucene] via GitHub
• [I] What were these bugs about? [lucene] via GitHub
  • Re: [I] What were these bugs about? [lucene] via GitHub
  • Re: [I] What were these bugs about? [lucene] via GitHub
• [I] LUCENE Jira board usage. [lucene] via GitHub
  • Re: [I] LUCENE Jira board usage. [lucene] via GitHub
  • Re: [I] LUCENE Jira board usage. [lucene] via GitHub
  • Re: [I] LUCENE Jira board usage. [lucene] via GitHub
• [PR] Make ./gradlew eclipse regenerate the same file [lucene] via GitHub
  • Re: [PR] Make ./gradlew eclipse regenerate the same file [lucene] via GitHub
• [PR] Make WrapperDownloader work for java >= 11 [lucene] via GitHub
  • Re: [PR] Make WrapperDownloader work for java >= 11 [lucene] via GitHub
• [I] WrapperDownloader does not work with java < 23 [lucene] via GitHub
  • Re: [I] WrapperDownloader does not work with java < 23 [lucene] via GitHub
• [PR] When doing something with gradle, don't reuse any caches [lucene] via GitHub
  • Re: [PR] When doing something with gradle, don't reuse any caches [lucene] via GitHub
  • Re: [PR] When doing something with gradle, don't reuse any caches [lucene] via GitHub
• [PR] NumericComparator: immediately check whether a segment is comparative with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
  • Re: [PR] NumericComparator: immediately check whether a segment is competitive with the recorded bottom [lucene] via GitHub
• [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
  • Re: [PR] Gradle 9.1+ doesn't allow exclusiveContent in pluginManagement repositories [lucene] via GitHub
• [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
  • Re: [PR] build: vscode improvements and devcontainer support [lucene] via GitHub
• [I] build: make "gradlew eclipse" idempotent [lucene] via GitHub
  • Re: [I] build: make "gradlew eclipse" idempotent [lucene] via GitHub
  • Re: [I] build: make "gradlew eclipse" idempotent [lucene] via GitHub
  • Re: [I] build: make "gradlew eclipse" idempotent [lucene] via GitHub
• [PR] Remove some exclusions from formatting generated Java files [lucene] via GitHub
  • Re: [PR] Remove some exclusions from formatting generated Java files [lucene] via GitHub
• [PR] ci: bump actions/upload-artifact from 4.6.2 to 5.0.0 [lucene] via GitHub
  • Re: [PR] ci: bump actions/upload-artifact from 4.6.2 to 5.0.0 [lucene] via GitHub
• [PR] build(deps): bump ruff from 0.14.1 to 0.14.2 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump ruff from 0.14.1 to 0.14.2 in /dev-tools/scripts [lucene] via GitHub
• [PR] build(deps): bump basedpyright from 1.31.7 to 1.32.1 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump basedpyright from 1.31.7 to 1.32.1 in /dev-tools/scripts [lucene] via GitHub
• [PR] build(deps): bump holidays from 0.82 to 0.83 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.82 to 0.83 in /dev-tools/scripts [lucene] via GitHub
• [I] Move StageArtifacts.java to build-tools [lucene] via GitHub
  • Re: [I] Move StageArtifacts.java to build-tools [lucene] via GitHub
• Re: [PR] Optimize prefix sum computation in Lucene99HnswVectorsReader; fixes #15024 [lucene] via GitHub
  • Re: [PR] Optimize prefix sum computation in Lucene99HnswVectorsReader; fixes #15024 [lucene] via GitHub
  • Re: [PR] Optimize prefix sum computation in Lucene99HnswVectorsReader; fixes #15024 [lucene] via GitHub
  • Re: [PR] Optimize prefix sum computation in Lucene99HnswVectorsReader; fixes #15024 [lucene] via GitHub
• Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
• Re: [PR] Add asynchronous prefetch for DirectIO directory [lucene] via GitHub
• [I] [RFC] Add support for Concurrent SegmentReader Initialization in DirectoryReader.open() [lucene] via GitHub
  • Re: [I] [RFC] Add support for Concurrent SegmentReader Initialization in DirectoryReader.open() [lucene] via GitHub
• [PR] Speed up java formatting tasks [lucene] via GitHub
  • Re: [PR] Speed up java formatting tasks [lucene] via GitHub
  • Re: [PR] Speed up java formatting tasks [lucene] via GitHub
  • Re: [PR] Speed up java formatting tasks [lucene] via GitHub
  • Re: [PR] Speed up java formatting tasks [lucene] via GitHub
  • Re: [PR] Speed up java formatting tasks [lucene] via GitHub
  • Re: [PR] Speed up java formatting tasks [lucene] via GitHub
  • Re: [PR] Speed up java formatting tasks [lucene] via GitHub
• [I] Review regeneration.txt after changes on main [lucene] via GitHub
  • Re: [I] Review regeneration.txt after changes on main [lucene] via GitHub
• [PR] Enable configuration cache (test tasks) [lucene] via GitHub
  • Re: [PR] Enable configuration cache (test tasks) [lucene] via GitHub
  • Re: [PR] Enable configuration cache (test tasks) [lucene] via GitHub
  • Re: [PR] Enable configuration cache (test tasks) [lucene] via GitHub
• [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub
  • Re: [PR] Support DocIdSetBuilder with partition bounds [lucene] via GitHub

• Earlier messages
• Later messages