Diptanu Choudhury
Diptanu Choudhury
@sadath-12 Please share some steps to reproduce. Don't have enough information about how to reproduce the error.
cc @Default2882
@yaarAdarsh Feel free to work on it. Generally Server 1. Write tests 2. Run the graph_behaviours.py integration tests 3. Write a test plan of how they tested the features.
Routers allow dynamic branching in Graphs. Such as going from file upload to structured extraction if the file is text, otherwise the file upload function can route to layout detector,...
Some pointers - 1. I had started the SDK work here - https://github.com/tensorlakeai/tensorlake/pull/79 2. We can remove routers in server data structure here - https://github.com/tensorlakeai/indexify/blob/5909fdc4f847c946d855eaee615ade3e56195948/server/data_model/src/lib.rs#L378 This will simplify a bunch...
We probably don't need the protocol to be extended. We get the Application spec in the executor, if the executor sees a blocking call go through for a function, it...
This is semi complete. We are getting function execution duration in the server now, but we don't push them out anywhere. We need to publish these usage metrics to SQS...
We need more validators for the graphs - 1. Ensure the output of a node is what the edges accept.
> When deploying a new graph version we need to shutdown FEs for the previous version to not 2x capacity for the current version and previous version. I think the...
Some more thoughts on this feature - 1. We don't bring up new graphs until there is enough capacity for all the replicas of function 2. Introduce the notion of...