You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am occasionally seeing the following stacktrace in my Staticman server logs, resulting in an HTTP 400 response to the frontend and a comment that fails to post. I haven't dived into Staticman's source code before, so before I do I thought I'd ask if anyone else has seen this, and knows whether the JSON that it's referencing is likely to be from the user end, or from Github or Akismet? Unfortunately Staticman doesn't log the problematic JSON string itself.
SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at parse (/workspace/node_modules/body-parser/lib/types/json.js:89:19)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
at endReadableNT (node:internal/streams/readable:1358:12)
at IncomingMessage.emit (node:domain:489:12)
at IncomingMessage.emit (node:events:525:35)
at IncomingMessage.onEnd (/workspace/node_modules/raw-body/index.js:280:7)
at done (/workspace/node_modules/raw-body/index.js:220:7)
at invokeCallback (/workspace/node_modules/raw-body/index.js:231:16)
at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
at /workspace/node_modules/body-parser/lib/read.js:128:18
Thanks
The text was updated successfully, but these errors were encountered:
Hi,
I am occasionally seeing the following stacktrace in my Staticman server logs, resulting in an HTTP 400 response to the frontend and a comment that fails to post. I haven't dived into Staticman's source code before, so before I do I thought I'd ask if anyone else has seen this, and knows whether the JSON that it's referencing is likely to be from the user end, or from Github or Akismet? Unfortunately Staticman doesn't log the problematic JSON string itself.
Thanks
The text was updated successfully, but these errors were encountered: