Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] JSON file bugs

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] JSON file bugs


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Allan Feng <>, "" <>
  • Subject: Re: [perfsonar-user] JSON file bugs
  • Date: Thu, 15 Aug 2019 17:20:12 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/PY2zNcWKfug4o7ByI1dHVrNPLNhIb9UsaYu/t7etoY=; b=ft+6c6rI0uAKvVGEkjh05gynjoRkWw7uyXNg28zDYI9ycux9NWrudHFL/lcE6yykxOH3qtbR0kbgDNDsT2hLFs9/2uQOTDOSn3eYdDjkZKpJhEtDnowJd04pMU+yAWJBpVD3yP92HnYHo+htFLYwsVYMIwPRZtez09IPZ6Vc1vkOaRtC7BJsq1+mVMWwmgwEoAgiTRgTAqYaL4ztA66xZMtDdTwA8b2oGVfweSu0Pit1pXeanpW+sVJYor6lwMJTutij+AZF9yxms3aZXo5sP93Jwvl8MDOLWCuL0KULv/uiW0A0kS00qCpaP3+Qj7YXfmj97NJ/bkSEesb/0cxW9Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=S+qd+07MpneuaDUmGqkbYJufN8kDa+XgTPk4TH5NEQc3DCdWds80eBVrNjIhuFN7C5OOzjuv1IBOuTTGQbk1nIjbH7aRw/qmRZAV2zQaXzmkRiXRl1dIglqE2USzqB5h5gJJmeszRSDaPDZv2Qdk38qeMDf1CMM8awUUv8coFxqFoXXCpktOhaNS37CYzpJmoiI4EgtUO+Br5S0TVEAagLxRj4whZ66MS6loElht2D1ZMtj+dRzWkf1hK7tbLxG42opdtSwYL5oPzalKkgoq22MrHUDb9b0lhltZmx5kF7VfdGqURT7xvaezg8hrRc3WqxlP8hDFPAlhQ+boVJEigA==

Allan Feng writes:

 

Hello, I've set up my maddash dashboard and I've getting the following errors,

 

" json.object cannot be cast to jason.lang.string"

 

Here is the attached files, any insight would help immensely, thank you!

 

The JSON file has a syntax error; line 14 has a trailing comma after the last element in the array which shouldn’t be there.

 

ProTip:  You can check a JSON file for validity on the command line by running “jq empty /path/to/file”.  Valid JSON will produce no output and jq will exit with a status of 0; invalid JSON will produce an error on standard error and a non-zero (usually 4) exit code.

 

I’ll see about getting a more-helpful error message in place.

 

--Mark

 


Archive powered by MHonArc 2.6.19.

Top of Page