[GODRIVER-1521] Extended JSON $scope prone to panics Created: 03/Mar/20  Updated: 11/Mar/20  Resolved: 11/Mar/20

Status: Closed
Project: Go Driver
Component/s: JSON & ExtJSON
Affects Version/s: 1.3.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: David Golden Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to GODRIVER-1520 Extended JSON lone $scope does not error Closed

 Description   

As mentioned in GODRIVER-1520, $scope can trigger panics. Here are additional examples:

{"":{"$scope":{
 
{"":{"":{"$scope":{
 
{"":[{"$scope":{
 
{"":[[[[{"$scope":{
 
{"":[[[[[[{"$scope":{



 Comments   
Comment by Divjot Arora (Inactive) [ 11/Mar/20 ]

This seems to be the same as GODRIVER-1520. A lone $scope will error because the extended JSON parser is assuming that it's already read a $code value. I'm going to make a change that will cause $scope values to error in the work for GODRIVER-1520 and include these inputs as test cases for that change.

Comment by David Golden [ 03/Mar/20 ]

I didn't look closely at GODRIVER-1500, just tarred up the data. I suspect that you can close GODRIVER-1500 and rely on the more specific tickets I've opened.

Comment by Jeffrey Yemin [ 03/Mar/20 ]

Is this different than GODRIVER-1500? Most of the crashers in there seem to include some usage of $scope.

Generated at Thu Feb 08 08:36:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.