repo string | instance_id string | base_commit string | patch string | test_patch string | problem_statement string | hints_text string | created_at string | version string | FAIL_TO_PASS sequence | PASS_TO_PASS sequence |
|---|---|---|---|---|---|---|---|---|---|---|
apache/druid | apache__druid-13704 | 51dfde02840017092486fb75be2b16566aff6a19 | diff --git a/docs/querying/post-aggregations.md b/docs/querying/post-aggregations.md
index c75d122eb20a..935ca8fbce16 100644
--- a/docs/querying/post-aggregations.md
+++ b/docs/querying/post-aggregations.md
@@ -36,7 +36,7 @@ There are several post-aggregators available.
The arithmetic post-aggregator applies the provi... | diff --git a/processing/src/test/java/org/apache/druid/query/aggregation/post/ArithmeticPostAggregatorTest.java b/processing/src/test/java/org/apache/druid/query/aggregation/post/ArithmeticPostAggregatorTest.java
index a93034427539..7e1d4d112b40 100644
--- a/processing/src/test/java/org/apache/druid/query/aggregation/p... | Support Post aggregation function pow(f1,f2) to cater for square, cube , square root.
### Description
Please describe the feature or change with as much detail as possible.
As of now the only supported arithmetic functions are +, -, *, /, and quotient.
https://druid.apache.org/docs/latest/querying/post-aggregat... | 2023-01-23 04:10:47 | 13704 | [
"org.apache.druid.query.aggregation.post.ArithmeticPostAggregatorTest#testPow"
] | [
"org.apache.druid.query.aggregation.post.ArithmeticPostAggregatorTest#testDiv",
"org.apache.druid.query.aggregation.post.ArithmeticPostAggregatorTest#testQuotient"
] | |
apache/druid | apache__druid-14092 | 4fffee17761286996a8c43154b72db4bcaafb16d | diff --git a/server/src/main/java/org/apache/druid/discovery/DruidLeaderClient.java b/server/src/main/java/org/apache/druid/discovery/DruidLeaderClient.java
index 0679ac39e4ac..3bc29da40f46 100644
--- a/server/src/main/java/org/apache/druid/discovery/DruidLeaderClient.java
+++ b/server/src/main/java/org/apache/druid/di... | diff --git a/server/src/test/java/org/apache/druid/discovery/DruidLeaderClientTest.java b/server/src/test/java/org/apache/druid/discovery/DruidLeaderClientTest.java
index 570720db48ff..6b8f32ba1906 100644
--- a/server/src/test/java/org/apache/druid/discovery/DruidLeaderClientTest.java
+++ b/server/src/test/java/org/apa... | DruidLeaderClient should refresh cache for non-200 responses
Currently DruidLeaderClient invalidates the cache when it encounters an IOException or a ChannelException ([here](https://github.com/apache/druid/blob/master/server/src/main/java/org/apache/druid/discovery/DruidLeaderClient.java#L160)). In environments where ... | 2023-04-14 21:01:40 | 14092 | [
"org.apache.druid.discovery.DruidLeaderClientTest#test503ResponseFromServerAndCacheRefresh"
] | [
"org.apache.druid.discovery.DruidLeaderClientTest#testServerFailureAndRedirect"
] | |
apache/druid | apache__druid-14136 | a7d4162195a630c380d75516c24229cc23e25271 | diff --git a/processing/src/main/java/org/apache/druid/java/util/common/JodaUtils.java b/processing/src/main/java/org/apache/druid/java/util/common/JodaUtils.java
index 5d15bfe717fe..54ec9411a2b2 100644
--- a/processing/src/main/java/org/apache/druid/java/util/common/JodaUtils.java
+++ b/processing/src/main/java/org/ap... | diff --git a/processing/src/test/java/org/apache/druid/common/utils/JodaUtilsTest.java b/processing/src/test/java/org/apache/druid/common/utils/JodaUtilsTest.java
index d7bfb4adffdc..2ee6bc31220b 100644
--- a/processing/src/test/java/org/apache/druid/common/utils/JodaUtilsTest.java
+++ b/processing/src/test/java/org/ap... | Zero-length interval matches too much data
On the example wikipedia dataset, this query matches all data after `2016-06-27T00:00:11.080Z`, but should really match nothing. The problem is in `VersionedIntervalTimeline.lookup` and stems from the fact that `interval1.overlaps(interval2)` does *not* consider the intervals ... | 2023-04-20 22:54:25 | 14136 | [
"org.apache.druid.timeline.VersionedIntervalTimelineTest#testOverlapSecondContainsFirstZeroLengthInterval",
"org.apache.druid.timeline.VersionedIntervalTimelineTest#testOverlapSecondContainsFirstZeroLengthInterval2",
"org.apache.druid.timeline.VersionedIntervalTimelineTest#testOverlapSecondContainsFirstZeroLeng... | [
"org.apache.druid.timeline.VersionedIntervalTimelineTest#testOverlapFirstContainsSecond",
"org.apache.druid.timeline.VersionedIntervalTimelineTest#testOverlapSecondContainsFirst"
] | |
apache/druid | apache__druid-15402 | 1df53d6eb30a019fff69a5ff7533ebbd998a438d | diff --git a/processing/src/main/java/org/apache/druid/query/groupby/GroupByQueryQueryToolChest.java b/processing/src/main/java/org/apache/druid/query/groupby/GroupByQueryQueryToolChest.java
index 9c746dd41429..96b8c7ec69f4 100644
--- a/processing/src/main/java/org/apache/druid/query/groupby/GroupByQueryQueryToolChest.... | diff --git a/processing/src/test/java/org/apache/druid/query/groupby/GroupByQueryQueryToolChestTest.java b/processing/src/test/java/org/apache/druid/query/groupby/GroupByQueryQueryToolChestTest.java
index 9b0a8e193af8..3a5a8d032afa 100644
--- a/processing/src/test/java/org/apache/druid/query/groupby/GroupByQueryQueryTo... | Druid 28.0.0 breaks the whole-query cache for groupBy queries with multiple post-aggregate metrics.
I have been using Druid 28.0.0 and found a new bug.
The whole-query cache for groupBy queries with multiple post-aggregation metrics is broken.
However, if there are no post-aggregation metrics or a single post-aggrega... | can you post your complete ingestion spec that you used to ingest the Wikipedia date?
seems like this is caused by restoring all postaggs into the same index during [pullFromCache](https://github.com/apache/druid/blob/ba1b6fa5a937e2f676e3c18944f6edec5b04d328/processing/src/main/java/org/apache/druid/query/groupby/Grou... | 2023-11-20 13:48:30 | 15402 | [
"org.apache.druid.query.groupby.GroupByQueryQueryToolChestTest#testCacheStrategy"
] | [
"org.apache.druid.query.groupby.GroupByQueryQueryToolChestTest#testResultLevelCacheKeyWithSubTotalsSpec",
"org.apache.druid.query.groupby.GroupByQueryQueryToolChestTest#testMultiColumnCacheStrategy"
] |
apache/druid | apache__druid-16875 | 483a03f26c7221f10493d86715985a58e61af967 | diff --git a/server/src/main/java/org/apache/druid/server/metrics/WorkerTaskCountStatsMonitor.java b/server/src/main/java/org/apache/druid/server/metrics/WorkerTaskCountStatsMonitor.java
index bc09e95b5ce9..a568ad85d423 100644
--- a/server/src/main/java/org/apache/druid/server/metrics/WorkerTaskCountStatsMonitor.java
+... | diff --git a/server/src/test/java/org/apache/druid/server/metrics/WorkerTaskCountStatsMonitorTest.java b/server/src/test/java/org/apache/druid/server/metrics/WorkerTaskCountStatsMonitorTest.java
index ad00e5e6dbde..a1930bef6379 100644
--- a/server/src/test/java/org/apache/druid/server/metrics/WorkerTaskCountStatsMonito... | WorkerTaskCountStatsMonitor doesn't work in Druid 30.0.0
### Affected Version
30.0.0
### Description
I'm using a Middlemanager+Peons and I used to have following monitors enabled in MM config:
```
druid.monitoring.monitors=["org.apache.druid.java.util.metrics.JvmMonitor", "org.apache.druid.server.metrics.Eve... | 2024-08-09 07:04:27 | 16875 | [
"org.apache.druid.server.metrics.WorkerTaskCountStatsMonitorTest#testMonitorWithPeon"
] | [
"org.apache.druid.server.metrics.WorkerTaskCountStatsMonitorTest#testMonitorWithNulls",
"org.apache.druid.server.metrics.WorkerTaskCountStatsMonitorTest#testMonitorIndexer"
] | |
apache/lucene | apache__lucene-11760 | 0ea8035612344e861bbdeaffca2255e5e1480a6a | diff --git a/lucene/queries/src/java/org/apache/lucene/queries/intervals/IntervalBuilder.java b/lucene/queries/src/java/org/apache/lucene/queries/intervals/IntervalBuilder.java
index b6e1727616c6..e76be6f9e609 100644
--- a/lucene/queries/src/java/org/apache/lucene/queries/intervals/IntervalBuilder.java
+++ b/lucene/que... | diff --git a/lucene/queries/src/test/org/apache/lucene/queries/intervals/TestIntervalBuilder.java b/lucene/queries/src/test/org/apache/lucene/queries/intervals/TestIntervalBuilder.java
index 3b6f63d98f56..b74670a51bcf 100644
--- a/lucene/queries/src/test/org/apache/lucene/queries/intervals/TestIntervalBuilder.java
+++ ... | IntervalBuilder.NO_INTERVALS returns wrong docId when unpositioned
### Description
DocIdSetIterators should return -1 when they are unpositioned, but
IntervalBuilder.NO_INTERVALS always returns NO_MORE_DOCS. This
can lead to exceptions when an empty interval query (for example, a
text string made entirely of stop... | 2022-09-09 14:36:21 | 11760 | [
"org.apache.lucene.queries.intervals.TestIntervalBuilder > testEmptyIntervals"
] | [
"org.apache.lucene.queries.intervals.TestIntervalBuilder > testUnordered",
"org.apache.lucene.queries.intervals.TestIntervalBuilder > testGraphSynonyms",
"org.apache.lucene.queries.intervals.TestIntervalBuilder > testGraphTerminatesOnGap",
"org.apache.lucene.queries.intervals.TestIntervalBuilder > testPhrase"... | |
apache/lucene | apache__lucene-12022 | 11f2bc205652f1f2b2f61ba286cbfd2d77fd2d1b | diff --git a/lucene/CHANGES.txt b/lucene/CHANGES.txt
index 132ce5cf82fe..56b0c818bdd9 100644
--- a/lucene/CHANGES.txt
+++ b/lucene/CHANGES.txt
@@ -195,6 +195,8 @@ Bug Fixes
* GITHUB#11986: Fix algorithm that chooses the bridge between a polygon and a hole when there is
common vertex. (Ignacio Vera)
+* GITHUB#1202... | diff --git a/lucene/core/src/test/org/apache/lucene/document/TestLatLonShape.java b/lucene/core/src/test/org/apache/lucene/document/TestLatLonShape.java
index 1e4caa129b80..b63a388c0812 100644
--- a/lucene/core/src/test/org/apache/lucene/document/TestLatLonShape.java
+++ b/lucene/core/src/test/org/apache/lucene/documen... | Very flat polygons give incorrect 'contains' result
### Description
When performing a search using a shape geometry query of relation type `QueryRelation.CONTAINS`, it is possible to get a false positive when two geometries intersect, but neither actually contains the other. This happens if the indexed geometry is a p... | 2022-12-15 11:05:42 | 12022 | [
"org.apache.lucene.document.TestLatLonShape > testFlatPolygonDoesNotContainIntersectingLine"
] | [
"org.apache.lucene.document.TestLatLonShape > testContainsWrappingBooleanQuery",
"org.apache.lucene.document.TestLatLonShape > testContainsGeometryCollectionIntersectsPolygon",
"org.apache.lucene.document.TestLatLonShape > testPointIndexAndQuery",
"org.apache.lucene.document.TestLatLonShape > testContainsGeom... | |
apache/lucene | apache__lucene-12196 | 0651d25713dde144df6541663b18accbc93cdc64 | diff --git a/lucene/CHANGES.txt b/lucene/CHANGES.txt
index 7391f2687573..0a0a265c8b0a 100644
--- a/lucene/CHANGES.txt
+++ b/lucene/CHANGES.txt
@@ -162,6 +162,8 @@ Bug Fixes
* GITHUB#12158: KeywordField#newSetQuery should clone input BytesRef[] to avoid modifying provided array. (Greg Miller)
+* GITHUB#12196: Fix M... | diff --git a/lucene/queryparser/src/test/org/apache/lucene/queryparser/classic/TestMultiFieldQueryParser.java b/lucene/queryparser/src/test/org/apache/lucene/queryparser/classic/TestMultiFieldQueryParser.java
index 57ed0e709729..ee684c30f85b 100644
--- a/lucene/queryparser/src/test/org/apache/lucene/queryparser/classic... | Slop is missing when boost is passed to MultiFieldQueryParser (Since Lucene 5.4.0)
### Description
On Lucene 5.3.2, If I run
```java
String[] fields = new String[]{ "field1"};
Analyzer analyzer = new StandardAnalyzer();
Map<String, Float> boosts = Map.of("field1", 1.5f);
MultiFieldQueryParser parser = new MultiF... | Tracked down the issue to this: In Lucene 5.4.0 [this commit](https://github.com/apache/lucene/commit/962313b83ba9c69379e1f84dffc881a361713ce9#diff-e10af886a9a7ba5221abfcfbe9dc057d2cee39d3b875e0eb2843085979ecdf5e) introduced some changes for immutability of queries. `setBoost()` function was replaced with `new BoostQue... | 2023-03-08 14:13:50 | 12196 | [
"org.apache.lucene.queryparser.classic.TestMultiFieldQueryParser > testBoostsSimple"
] | [
"org.apache.lucene.queryparser.classic.TestMultiFieldQueryParser > testStaticMethod2Old",
"org.apache.lucene.queryparser.classic.TestMultiFieldQueryParser > testSimpleRegex",
"org.apache.lucene.queryparser.classic.TestMultiFieldQueryParser > testSynonyms",
"org.apache.lucene.queryparser.classic.TestMultiField... |
apache/lucene | apache__lucene-12212 | b84b360f588c60e2ebdcaa2ce2e6d49f99dd9deb | diff --git a/lucene/facet/src/java/org/apache/lucene/facet/DrillSidewaysScorer.java b/lucene/facet/src/java/org/apache/lucene/facet/DrillSidewaysScorer.java
index fc415e148978..c86432b30f7f 100644
--- a/lucene/facet/src/java/org/apache/lucene/facet/DrillSidewaysScorer.java
+++ b/lucene/facet/src/java/org/apache/lucene/... | diff --git a/lucene/facet/src/test/org/apache/lucene/facet/TestDrillSideways.java b/lucene/facet/src/test/org/apache/lucene/facet/TestDrillSideways.java
index 893bcdb5f54f..1280e2f75114 100644
--- a/lucene/facet/src/test/org/apache/lucene/facet/TestDrillSideways.java
+++ b/lucene/facet/src/test/org/apache/lucene/facet/... | Searches made via DrillSideways may miss documents that should match the query.
### Description
Hi,
I use `DrillSideways` quite heavily in a project of mine and it recently realized that sometimes some documents that *should* match a query do not, whenever at least one component of the `DrillDownQuery` involved w... | 2023-03-23 16:36:28 | 12212 | [
"org.apache.lucene.facet.TestDrillSideways > testDrillSidewaysSearchUseCorrectIterator"
] | [
"org.apache.lucene.facet.TestDrillSideways > testSometimesInvalidDrillDown",
"org.apache.lucene.facet.TestDrillSideways > testScorer",
"org.apache.lucene.facet.TestDrillSideways > testBasicWithCollectorManager",
"org.apache.lucene.facet.TestDrillSideways > testNoCaching",
"org.apache.lucene.facet.TestDrillS... | |
apache/lucene | apache__lucene-12626 | de820b67cc6d7fc90446affeb756e70a2ddf6b92 | diff --git a/lucene/CHANGES.txt b/lucene/CHANGES.txt
index 4bc30f2058bd..1cd7f4c3ced7 100644
--- a/lucene/CHANGES.txt
+++ b/lucene/CHANGES.txt
@@ -321,6 +321,8 @@ Bug Fixes
* GITHUB#12640: Ensure #finish is called on all drill-sideways collectors even if one throws a
CollectionTerminatedException (Greg Miller)
+*... | diff --git a/lucene/core/src/test/org/apache/lucene/index/TestIndexWriter.java b/lucene/core/src/test/org/apache/lucene/index/TestIndexWriter.java
index 5c0303d9f9e7..364f1cc37201 100644
--- a/lucene/core/src/test/org/apache/lucene/index/TestIndexWriter.java
+++ b/lucene/core/src/test/org/apache/lucene/index/TestIndexW... | segmentInfos.replace() doesn't set userData
### Description
Found that the [replace method](https://github.com/qcri/solr-6/blob/master/lucene/core/src/java/org/apache/lucene/index/SegmentInfos.java#L875-L878) doesn't set `userData` with the new user data from `other`. Unsure if this is an oversight, but if it is, I ... | 2023-10-06 12:43:10 | 12626 | [
"org.apache.lucene.index.TestIndexWriter > testGetCommitDataFromOldSnapshot"
] | [
"org.apache.lucene.index.TestIndexWriter > testGetCommitData",
"org.apache.lucene.index.TestIndexWriter > testEmptyDirRollback",
"org.apache.lucene.index.TestIndexWriter > testIds",
"org.apache.lucene.index.TestIndexWriter > testOtherFiles",
"org.apache.lucene.index.TestIndexWriter > testMergeAllDeleted",
... | |
apache/lucene | apache__lucene-13170 | 3f4413567d2d41ecee16fcfe2c91a4b84bec0df8 | diff --git a/lucene/analysis/opennlp/src/java/org/apache/lucene/analysis/opennlp/OpenNLPSentenceBreakIterator.java b/lucene/analysis/opennlp/src/java/org/apache/lucene/analysis/opennlp/OpenNLPSentenceBreakIterator.java
index e3c2fb78320a..d81b06fd90d4 100644
--- a/lucene/analysis/opennlp/src/java/org/apache/lucene/anal... | diff --git a/lucene/analysis/opennlp/src/test/org/apache/lucene/analysis/opennlp/TestOpenNLPSentenceBreakIterator.java b/lucene/analysis/opennlp/src/test/org/apache/lucene/analysis/opennlp/TestOpenNLPSentenceBreakIterator.java
index acd13da0037b..465d067070e9 100644
--- a/lucene/analysis/opennlp/src/test/org/apache/luc... | ArrayIndexOutOfBoundsException in OpenNLPSentenceBreakIterator
### Description
When calling [preceding ](https://github.com/apache/lucene/blob/0782535017c9e737350e96fb0f53457c7b8ecf03/lucene/analysis/opennlp/src/java/org/apache/lucene/analysis/opennlp/OpenNLPSentenceBreakIterator.java#L136) function from [OpenNLPSent... | [OpenNLPSentenceBreakIterator.patch.txt](https://github.com/apache/lucene/files/11038808/OpenNLPSentenceBreakIterator.patch.txt)
| 2024-03-09 09:24:47 | 13170 | [
"org.apache.lucene.analysis.opennlp.TestOpenNLPSentenceBreakIterator > testPrecedingWithTwoSentences"
] | [
"org.apache.lucene.analysis.opennlp.TestOpenNLPSentenceBreakIterator > testFirstPosition",
"org.apache.lucene.analysis.opennlp.TestOpenNLPSentenceBreakIterator > testThreeSentences",
"org.apache.lucene.analysis.opennlp.TestOpenNLPSentenceBreakIterator > testWhitespaceOnly",
"org.apache.lucene.analysis.opennlp... |
apache/lucene | apache__lucene-13301 | 0345fcabb3ceb71fb39c1aa77502bae220f259ca | diff --git a/lucene/core/src/java/org/apache/lucene/geo/Circle.java b/lucene/core/src/java/org/apache/lucene/geo/Circle.java
index ad01b359dba6..07c2fc5b25cb 100644
--- a/lucene/core/src/java/org/apache/lucene/geo/Circle.java
+++ b/lucene/core/src/java/org/apache/lucene/geo/Circle.java
@@ -77,7 +77,9 @@ public boolean ... | diff --git a/lucene/core/src/test/org/apache/lucene/document/BaseXYShapeTestCase.java b/lucene/core/src/test/org/apache/lucene/document/BaseXYShapeTestCase.java
index 5f42f280809f..711a5242fba5 100644
--- a/lucene/core/src/test/org/apache/lucene/document/BaseXYShapeTestCase.java
+++ b/lucene/core/src/test/org/apache/lu... | Reproducible failure in TestXYPoint.testEqualsAndHashCode
### Description
This failure is because when comparing float values using the `==` operation, `-0.0` is equal to `0.0`, but their hashcode is different. should we use `Float.compare` or `Float.floatToRawIntBits` instead of `==` for the compare? it seems to do t... | 2024-04-14 11:17:15 | 13301 | [
"org.apache.lucene.geo.TestXYPoint > testEqualsAndHashCode"
] | [] | |
apache/lucene | apache__lucene-13494 | ab291210db08276fef1b52bf7b840d431e96ce08 | diff --git a/lucene/CHANGES.txt b/lucene/CHANGES.txt
index baa53ed5d901..3053955144d4 100644
--- a/lucene/CHANGES.txt
+++ b/lucene/CHANGES.txt
@@ -283,6 +283,9 @@ Bug Fixes
* GITHUB#13463: Address bug in MultiLeafKnnCollector causing #minCompetitiveSimilarity to stay artificially low in
some corner cases. (Greg Mil... | diff --git a/lucene/facet/src/test/org/apache/lucene/facet/TestStringValueFacetCounts.java b/lucene/facet/src/test/org/apache/lucene/facet/TestStringValueFacetCounts.java
index 45e48c5abc74..5c9a1eea7b48 100644
--- a/lucene/facet/src/test/org/apache/lucene/facet/TestStringValueFacetCounts.java
+++ b/lucene/facet/src/te... | NullPointerException in StringValueFacetCounts when using MultiCollectorManager
### Description
When I use `MultiCollectorManager` which merges both `FacetsCollectorManager` and `TopScoreDocCollectorManager` with a query not matching any docs, I expect to get `0` as a facet count, but get NPE:
```
Cannot read the ... | 2024-06-17 12:54:11 | 13494 | [
"TestStringValueFacetCounts > testEmptyMatchset"
] | [
"TestStringValueFacetCounts > testStaleState",
"TestStringValueFacetCounts > testRandom",
"TestStringValueFacetCounts > testSparseMultiSegmentCase",
"TestStringValueFacetCounts > testBasicSingleValued",
"TestStringValueFacetCounts > testBasicMultiValued",
"TestStringValueFacetCounts > testMissingSegment",... | |
apache/lucene | apache__lucene-13704 | ce4f56e74ad1087df8bdc019fc09d1b40438e8b3 | diff --git a/lucene/CHANGES.txt b/lucene/CHANGES.txt
index ae15247ac23c..63390dd8f9f9 100644
--- a/lucene/CHANGES.txt
+++ b/lucene/CHANGES.txt
@@ -410,6 +410,9 @@ Bug Fixes
* GITHUB#13691: Fix incorrect exponent value in explain of SigmoidFunction. (Owais Kazi)
+* GITHUB#13703: Fix bug in LatLonPoint queries where... | diff --git a/lucene/test-framework/src/java/org/apache/lucene/tests/geo/BaseGeoPointTestCase.java b/lucene/test-framework/src/java/org/apache/lucene/tests/geo/BaseGeoPointTestCase.java
index d371292324d5..5c0c134fef3c 100644
--- a/lucene/test-framework/src/java/org/apache/lucene/tests/geo/BaseGeoPointTestCase.java
+++ ... | Narrow polygons close to latitude 90 do not match any points
### Description
I found an edge case were given an enough narrow polygon close to latitude, then it will not match any point even where theoretically the point should match. The issue is easy to re produce with the following test:
```
public void testN... | 2024-08-30 13:42:08 | 13704 | [
"TestLatLonDocValuesQueries > testNarrowPolygonCloseToNorthPole"
] | [
"TestLatLonDocValuesQueries > testSmallSetDistanceNotEmpty",
"TestLatLonDocValuesQueries > testRandomDistance",
"TestLatLonDocValuesQueries > testLowCardinality",
"TestLatLonDocValuesQueries > testRectBoundariesAreInclusive",
"TestLatLonDocValuesQueries > testBoxNull",
"TestLatLonDocValuesQueries > testMu... | |
google/gson | google__gson-1014 | 7719e73a108c450666613c279bedaed724cd9cc9 | diff --git a/gson/src/main/java/com/google/gson/internal/bind/JsonTreeReader.java b/gson/src/main/java/com/google/gson/internal/bind/JsonTreeReader.java
index 0121231567..387b29e9bf 100644
--- a/gson/src/main/java/com/google/gson/internal/bind/JsonTreeReader.java
+++ b/gson/src/main/java/com/google/gson/internal/bind/J... | diff --git a/gson/src/test/java/com/google/gson/internal/bind/JsonTreeReaderTest.java b/gson/src/test/java/com/google/gson/internal/bind/JsonTreeReaderTest.java
new file mode 100644
index 0000000000..f6a5bf33e8
--- /dev/null
+++ b/gson/src/test/java/com/google/gson/internal/bind/JsonTreeReaderTest.java
@@ -0,0 +1,50 @@... | Bug when skipping a value while using the JsonTreeReader
When using a `JsonReader` to read a JSON object, `skipValue()` skips the structure successfully.
```Java
@Test
public void testSkipValue_JsonReader() throws IOException {
try (JsonReader in = new JsonReader(new StringReader("{}"))) {
in.skipValue();
... | 2017-02-08 12:37:29 | 1014 | [
"com.google.gson.internal.bind.JsonTreeReaderTest#testSkipValue_emptyJsonObject",
"com.google.gson.internal.bind.JsonTreeReaderTest#testSkipValue_filledJsonObject"
] | [] | |
google/gson | google__gson-1093 | 0aaef0fd1bb1b9729543dc40168adfb829eb75a4 | diff --git a/gson/src/main/java/com/google/gson/stream/JsonWriter.java b/gson/src/main/java/com/google/gson/stream/JsonWriter.java
index e2fc19611d..8148816c2f 100644
--- a/gson/src/main/java/com/google/gson/stream/JsonWriter.java
+++ b/gson/src/main/java/com/google/gson/stream/JsonWriter.java
@@ -491,10 +491,10 @@ pub... | diff --git a/gson/src/test/java/com/google/gson/stream/JsonWriterTest.java b/gson/src/test/java/com/google/gson/stream/JsonWriterTest.java
index 34dc914022..2bcec173ca 100644
--- a/gson/src/test/java/com/google/gson/stream/JsonWriterTest.java
+++ b/gson/src/test/java/com/google/gson/stream/JsonWriterTest.java
@@ -16,11... | JsonWriter#value(java.lang.Number) can be lenient, but JsonWriter#value(double) can't,
In lenient mode, JsonWriter#value(java.lang.Number) can write pseudo-numeric values like `NaN`, `Infinity`, `-Infinity`:
```java
if (!lenient
&& (string.equals("-Infinity") || string.equals("Infinity") || string.equals... | Can you create a Pull Request with a JUnit test that fails? Even better would be a fix that makes the test pass. Thanks. | 2017-05-31 08:22:46 | 1093 | [
"com.google.gson.stream.JsonWriterTest#testNonFiniteDoublesWhenLenient"
] | [
"com.google.gson.stream.JsonWriterTest#testNonFiniteBoxedDoublesWhenLenient",
"com.google.gson.stream.JsonWriterTest#testNonFiniteDoubles",
"com.google.gson.stream.JsonWriterTest#testNonFiniteBoxedDoubles",
"com.google.gson.stream.JsonWriterTest#testDoubles"
] |
google/gson | google__gson-1100 | f0aa1118e9ef66ed324f9a63cdfb551cb4e9eca5 | diff --git a/gson/src/main/java/com/google/gson/DefaultDateTypeAdapter.java b/gson/src/main/java/com/google/gson/DefaultDateTypeAdapter.java
index 95eb42bea3..3ce97fe89f 100644
--- a/gson/src/main/java/com/google/gson/DefaultDateTypeAdapter.java
+++ b/gson/src/main/java/com/google/gson/DefaultDateTypeAdapter.java
@@ -8... | diff --git a/gson/src/test/java/com/google/gson/DefaultDateTypeAdapterTest.java b/gson/src/test/java/com/google/gson/DefaultDateTypeAdapterTest.java
index b3ee5a6f4f..3c787a665f 100644
--- a/gson/src/test/java/com/google/gson/DefaultDateTypeAdapterTest.java
+++ b/gson/src/test/java/com/google/gson/DefaultDateTypeAdapte... | call new GsonBuilder().setDateFormat("yyyy-MM-dd").create().toJson exception.[2.8.1]
when a pojo object with null-value field and use "GsonBuilder().setDateFormat("yyyy-MM-dd")",will throw exception.
code:
//data class
class Person{
private Date age;
//getter setter
}
//demo
Gson gson = new GsonBuilder(... | 2017-06-08 16:46:09 | 1100 | [
"com.google.gson.DefaultDateTypeAdapterTest#testNullValue"
] | [
"com.google.gson.DefaultDateTypeAdapterTest#testDatePattern",
"com.google.gson.DefaultDateTypeAdapterTest#testInvalidDatePattern"
] | |
google/gson | google__gson-2024 | 16b42ff5805074126c2e5484450c182773e408a2 | diff --git a/gson/src/main/java/com/google/gson/FieldNamingPolicy.java b/gson/src/main/java/com/google/gson/FieldNamingPolicy.java
index 16e7124f45..a4fa7c2715 100644
--- a/gson/src/main/java/com/google/gson/FieldNamingPolicy.java
+++ b/gson/src/main/java/com/google/gson/FieldNamingPolicy.java
@@ -44,7 +44,7 @@ public ... | diff --git a/gson/src/test/java/com/google/gson/FieldNamingPolicyTest.java b/gson/src/test/java/com/google/gson/FieldNamingPolicyTest.java
index a62bae3aad..4d4c716b1e 100644
--- a/gson/src/test/java/com/google/gson/FieldNamingPolicyTest.java
+++ b/gson/src/test/java/com/google/gson/FieldNamingPolicyTest.java
@@ -67,7 ... | New FieldNamingPolicy: UPPER_CASE_WITH_UNDERSCORES
Hi,
currently, I do try to integrate a service that uses a UPPER_CASE_WITH_UNDERSCORES naming scheme for their field names, e.g.:
```
{
"PRODUCT_LIST" : {
"PRODUCT" : [
{
"APPLICATION_CODE" : "secret application code",
"PRODUCT_TYPE"... | Hi, we will volunteer to work on this issue in October/November. For the project maintainer, please let us know if this is okay and if you want it fixed. | 2021-11-22 03:35:03 | 2024 | [
"com.google.gson.functional.FieldNamingTest#testUpperCaseWithUnderscores",
"com.google.gson.functional.NamingPolicyTest#testGsonWithUpperCaseUnderscorePolicySerialization",
"com.google.gson.functional.NamingPolicyTest#testGsonWithUpperCaseUnderscorePolicyDeserialiation"
] | [] |
google/gson | google__gson-2061 | be0a1f4ff74bcd01580887cc9f3ec592d773f24c | diff --git a/gson/src/main/java/com/google/gson/internal/bind/JsonTreeReader.java b/gson/src/main/java/com/google/gson/internal/bind/JsonTreeReader.java
index f8238bc28b..a753402ed1 100644
--- a/gson/src/main/java/com/google/gson/internal/bind/JsonTreeReader.java
+++ b/gson/src/main/java/com/google/gson/internal/bind/J... | diff --git a/gson/src/test/java/com/google/gson/internal/bind/JsonTreeReaderTest.java b/gson/src/test/java/com/google/gson/internal/bind/JsonTreeReaderTest.java
index f6a5bf33e8..1166381bc8 100644
--- a/gson/src/test/java/com/google/gson/internal/bind/JsonTreeReaderTest.java
+++ b/gson/src/test/java/com/google/gson/int... | JsonReader.hasNext() returns true at END_DOCUMENT
JsonReader.hasNext() will return true if we are at the end of the document
(reader.peek() == JsonToken.END_DOCUMENT)
| It is not so much that `hasNext()` returns true (which seems correct anyway) as the fact that `skipValue()` fails to skip `END_DOCUMENT`:
```java
@Test
public void skipValue_does_not_skip_END_DOCUMENT ()
throws IOException
{
try (JsonReader jsonReader = new JsonReader(new StringReader("{}")))
{
... | 2022-01-23 01:03:06 | 2061 | [
"com.google.gson.stream.JsonReaderTest#testHasNextEndOfDocument",
"com.google.gson.internal.bind.JsonTreeReaderTest#testHasNext_endOfDocument"
] | [
"com.google.gson.stream.JsonReaderTest#testReadEmptyObject",
"com.google.gson.stream.JsonReaderTest#testReadEmptyArray",
"com.google.gson.internal.bind.JsonTreeReaderTest#testSkipValue_emptyJsonObject",
"com.google.gson.internal.bind.JsonTreeReaderTest#testSkipValue_filledJsonObject"
] |
google/gson | google__gson-2134 | 96ab171eb48dcea94fd9b8f425f65c531e6c3aad | diff --git a/gson/src/main/java/com/google/gson/internal/bind/util/ISO8601Utils.java b/gson/src/main/java/com/google/gson/internal/bind/util/ISO8601Utils.java
index 99ec679a71..02454fe3d8 100644
--- a/gson/src/main/java/com/google/gson/internal/bind/util/ISO8601Utils.java
+++ b/gson/src/main/java/com/google/gson/intern... | diff --git a/gson/src/test/java/com/google/gson/internal/bind/util/ISO8601UtilsTest.java b/gson/src/test/java/com/google/gson/internal/bind/util/ISO8601UtilsTest.java
index bc0c9ec0f6..68db238aaf 100644
--- a/gson/src/test/java/com/google/gson/internal/bind/util/ISO8601UtilsTest.java
+++ b/gson/src/test/java/com/google... | ISO8061Utils.parse() accepts non-existent dates
# Gson version
2.9.0
# Java / Android version
```
java 16 2021-03-16
Java(TM) SE Runtime Environment (build 16+36-2231)
Java HotSpot(TM) 64-Bit Server VM (build 16+36-2231, mixed mode, sharing)
```
# Description
Apparently `ISO8061Utils.parse()` works in a v... | 2022-06-12 20:12:27 | 2134 | [
"com.google.gson.internal.bind.util.ISO8601UtilsTest#testDateParseInvalidDay",
"com.google.gson.internal.bind.util.ISO8601UtilsTest#testDateParseInvalidMonth"
] | [
"com.google.gson.internal.bind.util.ISO8601UtilsTest#testDateParseWithDefaultTimezone"
] | |
google/gson | google__gson-2158 | 796193d0326a2f44bc314bf24262732ea3e64014 | diff --git a/gson/src/main/java/com/google/gson/Gson.java b/gson/src/main/java/com/google/gson/Gson.java
index 666e5f8bd3..7edead76ec 100644
--- a/gson/src/main/java/com/google/gson/Gson.java
+++ b/gson/src/main/java/com/google/gson/Gson.java
@@ -398,7 +398,7 @@ private TypeAdapter<Number> doubleAdapter(boolean seriali... | diff --git a/gson/src/test/java/com/google/gson/functional/PrimitiveTest.java b/gson/src/test/java/com/google/gson/functional/PrimitiveTest.java
index 6d74cc29b3..c4c25f0072 100644
--- a/gson/src/test/java/com/google/gson/functional/PrimitiveTest.java
+++ b/gson/src/test/java/com/google/gson/functional/PrimitiveTest.ja... | Primitive type adapters don't perform numeric conversion during serialization
# Gson version
2.9.0
# Java / Android version
Java 17
# Description
The built-in adapters for primitive types don't perform numeric conversion for serialization. This is most obvious when using Gson's non-typesafe method `Gson.toJson... | 2022-07-26 15:20:13 | 2158 | [
"com.google.gson.functional.PrimitiveTest#testByteSerialization",
"com.google.gson.functional.PrimitiveTest#testShortSerialization",
"com.google.gson.functional.PrimitiveTest#testIntSerialization",
"com.google.gson.functional.PrimitiveTest#testLongSerialization",
"com.google.gson.functional.PrimitiveTest#te... | [
"com.google.gson.functional.PrimitiveTest#testPrimitiveIntegerAutoboxedSerialization",
"com.google.gson.functional.PrimitiveTest#testPrimitiveIntegerAutoboxedInASingleElementArraySerialization",
"com.google.gson.functional.PrimitiveTest#testReallyLongValuesSerialization",
"com.google.gson.functional.Primitive... | |
google/gson | google__gson-2311 | 9f26679e7a96f0bb9952c326b2d9f79ef03ea9f5 | diff --git a/gson/src/main/java/com/google/gson/JsonPrimitive.java b/gson/src/main/java/com/google/gson/JsonPrimitive.java
index 66dacfe523..fce9093fb6 100644
--- a/gson/src/main/java/com/google/gson/JsonPrimitive.java
+++ b/gson/src/main/java/com/google/gson/JsonPrimitive.java
@@ -180,8 +180,11 @@ public BigDecimal ge... | diff --git a/gson/src/test/java/com/google/gson/JsonPrimitiveTest.java b/gson/src/test/java/com/google/gson/JsonPrimitiveTest.java
index b5b96638c5..2494701214 100644
--- a/gson/src/test/java/com/google/gson/JsonPrimitiveTest.java
+++ b/gson/src/test/java/com/google/gson/JsonPrimitiveTest.java
@@ -300,10 +300,8 @@ publ... | JsonPrimitive#equals Method behaves incorrect when used with BigInteger
# Gson version
2.9.0
# Java / Android version
Eclipse Adoptium OpenJDK 64-Bit Server VM 17.0.2+8 on Linux
# Used tools
- [ ] Maven; version:
- [x] Gradle; version: 7.3.3
- [ ] ProGuard (attach the configuration file please); version... | Seems to be related to #904 | 2023-02-06 15:17:53 | 2311 | [
"com.google.gson.JsonPrimitiveTest#testEqualsIntegerAndBigInteger"
] | [
"com.google.gson.JsonPrimitiveTest#testLongEqualsBigInteger",
"com.google.gson.JsonPrimitiveTest#testEqualsAcrossTypes"
] |
google/gson | google__gson-2479 | 4dfae77af3d543bea2782f85a154cc070290f086 | diff --git a/UserGuide.md b/UserGuide.md
index ed2fdf3368..aaf948bc29 100644
--- a/UserGuide.md
+++ b/UserGuide.md
@@ -405,7 +405,9 @@ gson.registerTypeAdapter(MyType.class, new MyDeserializer());
gson.registerTypeAdapter(MyType.class, new MyInstanceCreator());
```
-`registerTypeAdapter` call checks if the type ada... | diff --git a/gson/src/test/java/com/google/gson/GsonBuilderTest.java b/gson/src/test/java/com/google/gson/GsonBuilderTest.java
index 0dfa92b790..278540b612 100644
--- a/gson/src/test/java/com/google/gson/GsonBuilderTest.java
+++ b/gson/src/test/java/com/google/gson/GsonBuilderTest.java
@@ -17,6 +17,7 @@
package com.go... | `GsonBuilder` should throw exception when trying to register adapter for `Object` or `JsonElement`
# Problem solved by the feature
`GsonBuilder` does not support overwriting the built-in adapters for `Object` and for `JsonElement` (and subclasses). This might not be obvious to users (see #1177).
https://github.com/go... | @Marcono1234
I started looking into the solution options. In my opinion, both should throw exception in these cases as overwriting the built-in adapters might open some unexpected behaviors (including the one mentioned in #1177).
What exception is more appropriate in this case:
1. UnsupportedOperationException
2... | 2023-08-25 19:28:05 | 2479 | [
"com.google.gson.GsonBuilderTest#testRegisterTypeAdapterForObjectAndJsonElements",
"com.google.gson.GsonBuilderTest#testRegisterTypeHierarchyAdapterJsonElements"
] | [
"com.google.gson.GsonBuilderTest#testModificationAfterCreate"
] |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 208