Response Error on Some Calls

[graphstory]

Response Error on Some Calls

[tbogosia]

Oh, also want to add (if it wasn't clear) I ran the unit tests in the included Theo XcodeWorkspace, not in my own project.

[tbogosia]

I believe that crash was due to there being no data in my database before, the tests are now reaching test_004_successfullyAddNodeWithOutLabels before crashing. Which makes a lot more sense, since I had believed the GET requests were working and the POST were the problem.

[tbogosia]

I've found the problem. The headers set by Theo were being changed somewhere before sending the request. I'm going to try to locate where that's happening, but the easy fix was making sure to send application/json header right before the request went out.

If I find that it's an error in the code I'll create a pull request, it may have just been a strange problem with my code.

[kwylez]

that's very strange. I'll start looking there as well. This is just for your POSTS right?

Sent from my iPhone

On Apr 18, 2015, at 11:32 AM, Travis Bogosian [email protected] wrote:

I've found the problem. The headers set by Theo were being changed somewhere before sending the request. I'm going to try to locate where that's happening, but the easy fix was making sure to send application/json header right before the request went out.

If I find that it's an error in the code I'll create a pull request, it may have just been a strange problem with my code.

—
Reply to this email directly or view it on GitHub.

[kwylez]

Put a breakpoint or log the additional headers property in the request class

Sent from my iPhone

On Apr 18, 2015, at 11:32 AM, Travis Bogosian [email protected] wrote:

I've found the problem. The headers set by Theo were being changed somewhere before sending the request. I'm going to try to locate where that's happening, but the easy fix was making sure to send application/json header right before the request went out.

If I find that it's an error in the code I'll create a pull request, it may have just been a strange problem with my code.

—
Reply to this email directly or view it on GitHub.

[tbogosia]

Yeah, I added

mutableRequest.setValue("application/json", forHTTPHeaderField: "Content-Type")

in the postResource method of Request.swift, where the mutable request is made, and everything was fine afterward.

It was coming out as application/www-x-form-urlencoded when I checked my data packages going out before. Not sure where the change happened, because in the initial construction it was definitely using /json for the .httpRequest.

[kwylez]

I'll create a new branch and if you can issue a PR for this change. It will be a few hours before I get home.

Sent from my iPhone

On Apr 18, 2015, at 11:44 AM, Travis Bogosian [email protected] wrote:

Yeah, I added

mutableRequest.setValue("application/json", forHTTPHeaderField: "Content-Type")
in the postResource method of Request.swift, where the mutable request is made, and everything was fine afterward.

It was coming out as application/www-x-form-urlencoded when I checked my data packages going out before. Not sure where the change happened, because in the initial construction it was definitely using /json for the .httpRequest.

—
Reply to this email directly or view it on GitHub.

[tbogosia]

No problem, will do.

[kwylez]

I created a new branch for your to PR to issue/post-header

[tbogosia]

Perfect, I'll PR soon

[tbogosia]

Hi again Cory,

I'm having a little trouble. I think I executed a cypher query that was
long-running on my database by accident. Now I can't access the database at
all and all of my queries are timing out. I'm guessing that the database is
still attempting to run the other queries and can't respond to my requests.
Is there anything I can do?

Thanks,
Travis

On Sun, Apr 19, 2015 at 12:04 PM, Cory D. Wiles [email protected]
wrote:

I created a new branch for your to PR to issue/post-header

—
Reply to this email directly or view it on GitHub
#6 (comment).

[jeremykendall]

Hey @tbogosia,

Looks like there was indeed an issue with your database. I've restarted the instance and you're back up and running again.

Whenever you think there might be an issue with your database, please shoot an email over to [email protected]. We're more than happy to get that sorted out for you. Thanks!

[tbogosia]

Wonderful, thanks Jeremy.
Is the issue something I can avoid in the future? Or just a fluke sort of
thing...

On Thu, Jun 11, 2015 at 5:05 PM, Jeremy Kendall [email protected]
wrote:

Hey @tbogosia https://github.com/tbogosia,

Looks like there was indeed an issue with your database. I've restarted
the instance and you're back up and running again.

Whenever you think there might be an issue with your database, please
shoot an email over to [email protected]. We're more than happy to
get that sorted out for you. Thanks!

—
Reply to this email directly or view it on GitHub
#6 (comment).

[jeremykendall]

Careful query construction and correct indexes and constraints help avoid this situation. Send your query over to [email protected] and we'll take a look at it for you, if you like.

[tbogosia]

Alright, thanks Jeremy. It's a complex one that I've been thinking over for
a bit. I'll send it over now.

On Thu, Jun 11, 2015 at 5:09 PM, Jeremy Kendall [email protected]
wrote:

Careful query construction and correct indexes and constraints help avoid
this situation. Send your query over to [email protected] and we'll
take a look at it for you, if you like.

—
Reply to this email directly or view it on GitHub
#6 (comment).