Says unprocessible entity, but still posts the data

[iolocWebsite]

[iolocWebsite]

[richcorbs]

I'm getting the same thing from CURL and javascript FETCH.

[oddboy]

ascii.log Another one here. curl and also using the jsonbin Web Service (AutoWeb) for Tasker.

curl --version curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.36 zlib/1.2.7 libidn/1.28 libssh2/1.4.3 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz unix-sockets

AutoWeb (v 1.0.beta.2) + Tasker 5.8.5

Attaching a curl --trace-ascii ascii.log here for more info. This happens no matter what client i use. my very basic json validates on a number of online json validators and parsers. It's basically:

{ "Location": "Home" }

...I also get 422 when I copy/paste the examples from the jsonbin.org help page.

[virtualdj]

Same for me, like @oddboy with Tasker 5.9.1 and AutoWeb 1.0.beta2!

[ekkis]

is this service no longer supported?

[remy]

It was free from the outset so there was never any support. But it's also open source which means that we can all make it better of there's a problem we face.

I hope that answers your question.

[ekkis]

it does, thank you. I spent a bit of time with the source trying to figure out where the issue emanates but I'm limited on the time I can devote to it. the problem occurs on a base usecase and needs some attention. for now I'm just ignoring the return value and reissuing a query to make sure the value got written down but that's not a good thing to do. I've opened a separate issue on this

[remy]

I may have found the root cause of this - mongoose doesn't might be trying to write in parallel on the same record. I've added a promise to handle this potential situation and will close this issue for the time being (in the vague hope it's fixed :))