Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#4692 closed defect (wontfix)

Errors when getting large relation history

Reported by: don-vip Owned by: rails-dev@…
Priority: major Milestone:
Component: api Version:
Keywords: Cc:


When requesting this history:


After a long time, I received first the following HTTP 500 error:

<h1>Internal Server Error</h1>
<p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p>
<p>Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
<address>Apache/2.2.22 (Ubuntu) Server at Port 80</address>

I tried again and had this time a memory error:

NoMemoryError: failed to allocate memory

Change History (2)

comment:1 Changed 7 years ago by Tom Hughes

Resolution: wontfix
Status: newclosed

Not much we can do about this I'm afraid - some relations are so massive it's pretty much impossible to the ruby API to return them especially when you ask for the full history.

Hopefully one day this will all be moved to cgimap and there will be a better chance of being able to fetch it.

comment:2 Changed 7 years ago by don-vip

So currently, the only way to consult history of such relations is to iterate on each version until the API returns a version not found ?

Is there hope to see some of my requests [1] concerning summarized history data implemented in the next API ?


Note: See TracTickets for help on using tickets.