issues  

Messages by Thread

• • Re: [PR] build: move forbidden-apis and more to java [lucene] via GitHub
  • Re: [PR] build: move forbidden-apis and more to java [lucene] via GitHub
  • Re: [PR] build: move forbidden-apis and more to java [lucene] via GitHub
  • Re: [PR] build: move forbidden-apis and more to java [lucene] via GitHub
  • Re: [PR] build: move forbidden-apis and more to java [lucene] via GitHub
• [PR] Test format bot violations [lucene] via GitHub
  • Re: [PR] Test format bot violations [lucene] via GitHub
  • Re: [PR] Test format bot violations [lucene] via GitHub
  • Re: [PR] Test format bot violations [lucene] via GitHub
  • Re: [PR] Test format bot violations [lucene] via GitHub
• [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
  • Re: [PR] Updating Dense#intoBitSet to properly set upTo if it exceeds bitset size [lucene] via GitHub
• [PR] Feat/auto format workflow [lucene] via GitHub
  • Re: [PR] Feat/auto format workflow [lucene] via GitHub
  • Re: [PR] Feat/auto format workflow [lucene] via GitHub
• [PR] Avoid allocations in IndexFileNames.parseGeneration method [lucene] via GitHub
  • Re: [PR] Avoid allocations in IndexFileNames.parseGeneration method [lucene] via GitHub
  • Re: [PR] Avoid allocations in IndexFileNames.parseGeneration method [lucene] via GitHub
  • Re: [PR] Avoid allocations in IndexFileNames.parseGeneration method [lucene] via GitHub
  • Re: [PR] Avoid allocations in IndexFileNames.parseGeneration method [lucene] via GitHub
  • Re: [PR] Avoid allocations in IndexFileNames.parseGeneration method [lucene] via GitHub
  • Re: [PR] Avoid allocations in IndexFileNames.parseGeneration method [lucene] via GitHub
  • Re: [PR] Avoid allocations in IndexFileNames.parseGeneration method [lucene] via GitHub
  • Re: [PR] Avoid allocations in IndexFileNames.parseGeneration method [lucene] via GitHub
• Re: [PR] New JMH benchmark method - vdot8s that implement int8 dotProduct in C… [lucene] via GitHub
  • Re: [PR] New JMH benchmark method - vdot8s that implement int8 dotProduct in C… [lucene] via GitHub
  • Re: [PR] New JMH benchmark method - vdot8s that implement int8 dotProduct in C… [lucene] via GitHub
  • Re: [PR] New JMH benchmark method - vdot8s that implement int8 dotProduct in C… [lucene] via GitHub
  • Re: [PR] New JMH benchmark method - vdot8s that implement int8 dotProduct in C… [lucene] via GitHub
  • Re: [PR] New JMH benchmark method - vdot8s that implement int8 dotProduct in C… [lucene] via GitHub
  • Re: [PR] New JMH benchmark method - vdot8s that implement int8 dotProduct in C… [lucene] via GitHub
• [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
  • Re: [PR] build: use a faster and more robust source-patterns [lucene] via GitHub
• [PR] build: move missing-spi-block-tag out of source-patterns.gradle [lucene] via GitHub
  • Re: [PR] build: move missing-spi-block-tag out of source-patterns.gradle [lucene] via GitHub
  • Re: [PR] build: move missing-spi-block-tag out of source-patterns.gradle [lucene] via GitHub
  • Re: [PR] build: move missing-spi-block-tag out of source-patterns.gradle [lucene] via GitHub
  • Re: [PR] build: move missing-spi-block-tag out of source-patterns.gradle [lucene] via GitHub
• [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
  • Re: [PR] build: check vectors code with error-prone [lucene] via GitHub
• [PR] build: enable error-prone's FormatString check [lucene] via GitHub
  • Re: [PR] build: enable error-prone's FormatString check [lucene] via GitHub
  • Re: [PR] build: enable error-prone's FormatString check [lucene] via GitHub
  • Re: [PR] build: enable error-prone's FormatString check [lucene] via GitHub
  • Re: [PR] build: enable error-prone's FormatString check [lucene] via GitHub
  • Re: [PR] build: enable error-prone's FormatString check [lucene] via GitHub
  • Re: [PR] build: enable error-prone's FormatString check [lucene] via GitHub
  • Re: [PR] build: enable error-prone's FormatString check [lucene] via GitHub
• [PR] Run ecj in-process [lucene] via GitHub
  • Re: [PR] Run ecj in-process [lucene] via GitHub
  • Re: [PR] Run ecj in-process [lucene] via GitHub
  • Re: [PR] Run ecj in-process [lucene] via GitHub
  • Re: [PR] Run ecj in-process [lucene] via GitHub
  • Re: [PR] Run ecj in-process [lucene] via GitHub
  • Re: [PR] Run ecj in-process [lucene] via GitHub
  • Re: [PR] Run ecj in-process [lucene] via GitHub
  • Re: [PR] Run ecj in-process [lucene] via GitHub
• [PR] Bring back path linting [lucene] via GitHub
  • Re: [PR] Bring back path linting [lucene] via GitHub
• [PR] Remove a few more boolean success flags [lucene] via GitHub
  • Re: [PR] Remove a few more boolean success flags [lucene] via GitHub
• [I] Do not add non-existing classpath files and folders (resource outputs from sourcesets, for example) [lucene] via GitHub
  • Re: [I] Do not add non-existing classpath files and folders (resource outputs from sourcesets, for example) [lucene] via GitHub
• [I] investigate if ECJ can/should run without forking? [lucene] via GitHub
  • Re: [I] investigate if ECJ can/should run without forking? [lucene] via GitHub
  • Re: [I] investigate if ECJ can/should run without forking? [lucene] via GitHub
  • Re: [I] investigate if ECJ can/should run without forking? [lucene] via GitHub
  • Re: [I] investigate if ECJ can/should run without forking? [lucene] via GitHub
• [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
  • Re: [PR] Vectorize bitset to array [lucene] via GitHub
• [PR] Rename the generated apijar files to -api.jar [lucene] via GitHub
  • Re: [PR] Rename the generated apijar files to -api.jar [lucene] via GitHub
  • Re: [PR] Rename the generated apijar files to -api.jar [lucene] via GitHub
  • Re: [PR] Rename the generated apijar files to -api.jar [lucene] via GitHub
  • Re: [PR] Rename the generated apijar files to -api.jar [lucene] via GitHub
  • Re: [PR] Rename the generated apijar files to -api.jar [lucene] via GitHub
• [PR] Deprecate MergeSpecification#segString(Directory) [lucene] via GitHub
  • Re: [PR] Deprecate MergeSpecification#segString(Directory) [lucene] via GitHub
  • Re: [PR] Deprecate MergeSpecification#segString(Directory) [lucene] via GitHub
  • Re: [PR] Fixes #14899 Deprecate MergeSpecification#segString(Directory) [lucene] via GitHub
  • Re: [PR] Fixes #14899 Deprecate MergeSpecification#segString(Directory) [lucene] via GitHub
  • Re: [PR] Fixes #14899 Deprecate MergeSpecification#segString(Directory) [lucene] via GitHub
  • Re: [PR] Fixes #14899 Deprecate MergeSpecification#segString(Directory) [lucene] via GitHub
• [PR] build: enable more of javac 24's lints, fix some issues [lucene] via GitHub
  • Re: [PR] build: enable more of javac 24's lints, fix some issues [lucene] via GitHub
  • Re: [PR] build: enable more of javac 24's lints, fix some issues [lucene] via GitHub
  • Re: [PR] build: enable more of javac 24's lints, fix some issues [lucene] via GitHub
  • Re: [PR] build: enable more of javac 24's lints, fix some issues [lucene] via GitHub
  • Re: [PR] build: enable more of javac 24's lints, fix some issues [lucene] via GitHub
  • Re: [PR] build: enable more of javac 24's lints, fix some issues [lucene] via GitHub
  • Re: [PR] build: enable more of javac 24's lints, fix some issues [lucene] via GitHub
  • Re: [PR] build: enable more of javac 24's lints, fix some issues [lucene] via GitHub
• [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
  • Re: [PR] Use branchless way to speedup filterCompetitiveHits [lucene] via GitHub
• [PR] build: modernize the javadoc validation, part 1 [lucene] via GitHub
  • Re: [PR] build: modernize the javadoc validation, part 1 [lucene] via GitHub
  • Re: [PR] build: modernize the javadoc validation, part 1 [lucene] via GitHub
  • Re: [PR] build: modernize the javadoc validation, part 1 [lucene] via GitHub
  • Re: [PR] build: modernize the javadoc validation, part 1 [lucene] via GitHub
  • Re: [PR] build: modernize the javadoc validation, part 1 [lucene] via GitHub
  • Re: [PR] build: modernize the javadoc validation, part 1 [lucene] via GitHub
  • Re: [PR] build: modernize the javadoc validation, part 1 [lucene] via GitHub
  • Re: [PR] build: modernize the javadoc validation, part 1 [lucene] via GitHub
• [PR] build: fix malformed HTML generated by changes2html [lucene] via GitHub
  • Re: [PR] build: fix malformed HTML generated by changes2html [lucene] via GitHub
  • Re: [PR] build: fix malformed HTML generated by changes2html [lucene] via GitHub
• [PR] build: include overview.html into javadocs again [lucene] via GitHub
  • Re: [PR] build: include overview.html into javadocs again [lucene] via GitHub
  • Re: [PR] build: include overview.html into javadocs again [lucene] via GitHub
  • Re: [PR] build: include overview.html into javadocs again [lucene] via GitHub

• Earlier messages
• Later messages