Patches are welcomed :-D
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Jun 7, 2017 15:55, "Warren Young" wrote:
On Jun 7, 2017, at 7:38 AM, Stephan Beal wrote:
>
> BTW- there is an API
On Jun 7, 2017, at 7:38 AM, Stephan Beal wrote:
>
> BTW- there is an API intended just for checking whether json is built in:
> /json/HAI (from lolcatz jargon... it made sense at the time (2011)).
Then I have a new bug to file: it doesn’t respond KTHXBYE as it obviously
On Jun 7, 2017 03:59, "Warren Young" wrote:
That’s a much simpler call. It doesn’t require any permissions, and it’s a
GET call, not a POST call. That test proves little other than that you
have a working JSON API in your local Fossil instance.
BTW- there is an API
Thanks Warren,
The problem was related with the curled quotes. Now is working fine.
The simpler test was because I was getting "
curl: (6) Could not resolve host: -d
So I was interested in see the host resolution with a simpler command.
Cheers,
Offray
On 06/06/17 20:58, Warren Young wrote:
Sorry, that last one is wrong. Instead, change:
http://fossil-scm.org/index.html/artifact?ln=1385=cc8d06a2d208ad00
To:
while(0); tmp = 0
(with no trailing semicolon)
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Jun 7, 2017
Aaaand: add 1 line between these two:
http://fossil-scm.org/index.html/artifact?ln=1380-1381=cc8d06a2d208ad00
Add:
tmp = 0; \
To avoid a separate (potential) corner case bug.
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Jun 7,
The error is triggered here:
http://fossil-scm.org/index.html/artifact?ln=1518-1525=cc8d06a2d208ad00
Because of:
... Hmmm... i THINK (not certain) it's because json_respone_command_path()
is, via, json_create_response() returning null because of missing data in
g.json. It interprets that as an
Here we go:
http://fossil-scm.org/index.html/info/2accaaeeadd34cb6
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Jun 7, 2017 04:41, "Stephan Beal" wrote:
> Afaik, all errors except allocation failures do
Afaik, all errors except allocation failures do return the error in json
form (i had to jump through some hoops to get that working way back then,
due to fossil's fail-fast-via-exit() approach to error handling). The
mis-triggered alloc report here is, as you say, likely a side effect of
the null
On Jun 6, 2017, at 5:58 PM, Stephan Beal wrote:
>
> If you leave quotes off of the property names, it's not json
Yes, but that’s only one of the three problems here. The other two are:
1. It should diagnose the error correctly. (The error has nothing to do with
memory
On Jun 6, 2017, at 5:51 PM, Offray Vladimir Luna Cárdenas
wrote:
>
> When I try something similar with:
>
> curl -H "Content-Type: application/json" \ -d '{"authToken":
> "mytoken",\
>"payload": {"name": “foo", "content": "bar"}}'
>
If you leave quotes off of the property names, it's not json and the
request cannot be parsed at all. Why that shows up as a response allocation
error, i can't say off hand. It's a bug - the response should be that the
request is missing data/parameters.
- stephan
Sent from a mobile device,
Thanks Warren for your quick answer.
When I try something similar with:
curl -H "Content-Type: application/json" \ -d '{"authToken":
"mytoken",\
"payload": {"name": “foo", "content": "bar"}}'
http://localhost:8081/json/wiki/create
I get:
curl: (6) Could not
On Jun 6, 2017, at 1:09 PM, Offray Vladimir Luna Cárdenas
wrote:
>
> I don't know how the page name is supposed to be given in the URL.
The document you point to says it’s supposed to be sent in the payload, not in
the request URL:
$ curl -H "Content-Type:
14 matches
Mail list logo