Getting error from yesterday while trying to generate a schema for json

[mokshagna517]

Unable to generate a schema from yesterday. Getting error message for any kind of json on clicking the submit button. Pls restore the functionality.

[jtermine]

Definitely broken when trying to generate a schema. 500 error messages everywhere.

[jackwootton]

@mokshagna517 @jtermine Can you provide the JSON you're using or steps to reproduce, because, for me at least, I am unable to reproduce these errors.

[jtermine]

A screen print would probably help here.

The specific API call that is returning the 500 error in the screen print is a POST call to https://prod.json.systems/v1/graphs:inferGraph?key=AIzaSyDOzK6DXqsLvq57cxa5Y7o6_TkMZ1SS3bk

The body of the message

{
 "code": 2,
 "message": "Exception calling application: Incorrect padding",
 "details": [
  {
   "@type": "type.googleapis.com/google.rpc.DebugInfo",
   "stackEntries": [],
   "detail": "internal"
  }
 ]
}

[cabrinoob]

same error

[indiealexh]

Had the same issue, although clearing cache and hard reload helped. Will try recreate again.

Edit: After logging in as Guthub User issue reappears

Edit 2: After trying each login method, I found only github seems to have the issue. Also the http request is identical between each login method on submit of the JSON, only the Bearer token is different (For obvious reasons), seems like its some sort of auth error maybe. Can someone else try to replicate this too?

[Detnator-Neo]

Hello I'm getting the same error. I haven't looked into it as deeply as those screenshots do but my error is exactly the same (different key of course).

My json is particularly long. I'll try something smaller at some point, but wanted to report this now. My setup: Safari 13.1.2 and Safari Technology Preview 14.0.1 on macOS 10.15.6 Catalina. I also tried it in Chrome 85.0.4183.102 (same macOS), and that doesn't give me any error, it just spins its wheels indefinitely with no result (10 minutes or so so far).

I did get a result in Safari at one point. I've tried clearing all the website data (cache, cookies, etc) but still no go.

Hope this helps...?

[jackwootton]

@indiealexh @cabrinoob @jtermine Thank you for this information.

I'm pretty sure this is originating from the use of Python's base64.py module where it raises an error

 raise binascii.Error('Incorrect padding')

This module is only used to decode the result of authentication, conducted by the ESP, and made available in the X-Endpoint-API-UserInfo header (documented in Using Firebase to authenticate users). So for whatever reason, the ESP is not forwarding the authentication result in this header and so my the application will just return an error (since there is no way to authenticate the user)

Can you paste the bearer token into the debugger at jwt.io? You don't need to include the Bearer part, just the JWT that appears after it. This will at least tell you if the JWT is well formed.

If you don't want to share the decoded value on here, feel free to send it to info@jsonschema.net

[jackwootton]

@indiealexh @cabrinoob @jtermine @mokshagna517 I deployed a change this morning which may resolve the issue. If this does fix it, I'll add more detail here. Can you please give it go at www.jsonschema.net (force reload and empty cache)?

Thank you

[mfg92]

I had the same problem a week ago and now the side works again for me. Thank you @jsonsystems!

[wellingtonpgp]

I had the same problem today.. { "code": 2, "message": "Exception calling application: name 'binascii' is not defined", "details": [ { "@type": "type.googleapis.com/google.rpc.DebugInfo", "stackEntries": [], "detail": "internal" } ] }

[jackwootton]

I had the same problem today.. { "code": 2, "message": "Exception calling application: name 'binascii' is not defined", "details": [ { "@type": "type.googleapis.com/google.rpc.DebugInfo", "stackEntries": [], "detail": "internal" } ] }

@wellingtonpgp Are you still experiencing this problem?

[jackwootton]

@indiealexh @cabrinoob @jtermine @mokshagna517 is this now working for you?

[mokshagna517]

@indiealexh @cabrinoob @jtermine @mokshagna517 is this now working for you?

Hey @jsonsystems thanks..It is working now..I haven't used it for a while. Now it is ok. All good.