search

alterm4nn / ChronoZoom

ChronoZoom is an interactive timeline for all of history.
http://www.chronozoom.com
156 stars 124 forks source link

ProgressiveLoad: [Server] Fails to filter in the deep hierarchy #243

Open mirounga opened 11 years ago

mirounga commented 11 years ago

Repro steps:

Go to http://test.chronozoomproject.org/mirounga/eol/

Expected: Deep hierarchy of timelines (hundreds at least) all spanning 5KA - present Root timeline is "Metazoa"

Observed: A single timeline, evidently a leaf in the hierarchy.

jilarson commented 11 years ago

Currently if we load, we are not seeing the root timeline, we are seeing different leafs, and each user is seeing a different leaf.

M3tan3rd commented 11 years ago

I'm designating this authoring because this problem hides behind the new addition of especially deep content and end-users ability to create such content.

alterm4nn commented 11 years ago

http://test.chronozoomproject.org/api/gettimelines?start=-50000000000&end=9999&_=1370584738262 returns the following:

{"exception":"StorageCorruptedException","message":"Exception of type 'Chronozoom.Entities.StorageCorruptedException' was thrown.","stacktrace":" at Chronozoom.Entities.Storage.TimelineSubtreeQuery(Guid collectionId, Nullable1 leastCommonAncestor, Decimal startTime, Decimal endTime, Decimal minSpan, Int32 maxElements)\u000d\u000a at Chronozoom.UI.ChronozoomSVC.<>c__DisplayClass2.<GetTimelines>b__0(User user)\u000d\u000a at Chronozoom.UI.ChronozoomSVC.AuthenticatedOperation[T](Func2 operation)\u000d\u000a at Chronozoom.UI.ChronozoomSVC.GetTimelines(String superCollection, String collection, String start, String end, String minspan, String commonAncestor, String maxElements, String depth)\u000d\u000a at SyncInvokeGetTimelines(Object , Object[] , Object[] )\u000d\u000a at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)\u000d\u000a at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)\u000d\u000a at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)\u000d\u000a at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc)\u000d\u000a at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)\u000d\u000a at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)\u000d\u000a at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)\u000d\u000a at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)\u000d\u000a at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)\u000d\u000a at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)\u000d\u000a at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)"}

javierluraschi commented 11 years ago

I'll take a look at this one.

javierluraschi commented 11 years ago

@jilarson The timeout will also get fixed once we start using Yitaos stored proc.