Activity
From 04/12/2017 to 05/11/2017
05/11/2017
- 07:34 AM Feature #3277: implement call-graph v3
- > Do we really need in Janus to map the key as String? Because if instead of bld.addKey(prop, Mapping.STRING.asParame...
- 06:33 AM Feature #3277: implement call-graph v3
- Greg Shah wrote:
> > About the index issues: this code in JanusGraphDB.createIndexImpl needs to be changed, as compo... - 06:16 AM Feature #3277: implement call-graph v3
- > About the index issues: this code in JanusGraphDB.createIndexImpl needs to be changed, as composite indexes don't a...
- 06:15 AM Feature #3277: implement call-graph v3
- Constantin, please rework and extend the run_statements.rules, for each call-site:
* establish a "contains" edge f... - 06:07 AM Feature #3277: implement call-graph v3
- About the index issues: this code in @JanusGraphDB.createIndexImpl@ needs to be changed, as composite indexes don't a...
05/09/2017
- 05:56 PM Feature #3277: implement call-graph v3
- I've just checked in branch 1514a revision 11161 which is a shift to JanusGraph 0.2.0 and Tinkerpop 3.2.2 plus all th...
- 04:46 PM Feature #3277: implement call-graph v3
- >> add all entry points as full vertices in the database, with enough information to associate them back to the origi...
- 04:22 PM Feature #3277: implement call-graph v3
- From Greg:
> I need help with the expansion and rework of the core graph itself. The biggest areas are:
>
> ad... - 01:20 PM Feature #3277: implement call-graph v3
- Attached is the JanusGraph 0.2.0 javadoc which is not available on the Internet (at least as known by Google and by t...
05/05/2017
- 12:55 PM Feature #3277: implement call-graph v3
- Greg Shah wrote:
> As far as I can tell, the javadoc parameter is probably just a bit misleading. Am I missing some... - 10:38 AM Feature #3277: implement call-graph v3
- In @JanusGraphDB.createIndex*Impl()@, the @text@ parameter is described as this:...
05/02/2017
- 05:17 PM Feature #3277: implement call-graph v3
- Greg Shah wrote:
> In @link_to_include@ or @print_call_site@ we see this code: @cgw.edgeIterator(out, "include-locat... - 04:21 PM Feature #3277: implement call-graph v3
- In @link_to_include@ or @print_call_site@ we see this code: @cgw.edgeIterator(out, "include-location", "call-site-id"...
- 04:22 PM Feature #3225: windows vs linux in p2j.cfg.xml
- > use progress-style separators, this way being OS neutral
This seems to make good sense.
05/01/2017
- 11:01 AM Feature #1514: implement fully dynamic reports (backed by the database)
- Branch 1514a has been rebased from trunk 11150. The latest revision is 11155.
04/27/2017
- 12:40 PM Bug #2356 (New): pphints bug - nested includes are missing from the.pphints file
- OK, that makes sense.
- 12:19 PM Bug #2356: pphints bug - nested includes are missing from the.pphints file
- Greg Shah wrote:
> I've looked deeper at this. Expansions that are inside of preprocessor directives are deliberate... - 10:59 AM Bug #2356 (Rejected): pphints bug - nested includes are missing from the.pphints file
- I've looked deeper at this. Expansions that are inside of preprocessor directives are deliberately excluded from the...
04/26/2017
- 02:18 PM Feature #3277: implement call-graph v3
- Greg Shah wrote:
> 1. The @CGW.CallGraph.addTarget()@ does not add to the @traversed@ list. Is that expected?
I th... - 02:05 PM Feature #3277: implement call-graph v3
- 1. The @CGW.CallGraph.addTarget()@ does not add to the @traversed@ list. Is that expected?
2. I don't understand ...
04/21/2017
- 04:02 PM Feature #3277: implement call-graph v3
- Greg Shah wrote:
> >> a list of the linkages that need to be reworked into the "normalized" graph (where all linkage... - 02:53 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> No, I'll handle it.
OK. - 02:52 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- No, I'll handle it.
- 02:29 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg,
While I'm working on another task should I keep rebasing @1521c@ branch with the upcoming new trunk versions? - 03:03 AM Feature #1514: implement fully dynamic reports (backed by the database)
- Eric Faulhaber wrote:
> Hynek, I have a simple class which starts up a simple Jetty server with SSL, based on Greg's... - 10:55 PM Feature #1514: implement fully dynamic reports (backed by the database)
- Hynek Cihlar wrote:
> A few notes about the RPC. While I agree with Greg that the REST-like programming model isn't ...
04/20/2017
- 04:26 PM Feature #3277: implement call-graph v3
- >> a list of the linkages that need to be reworked into the "normalized" graph (where all linkage types are first cla...
- 04:09 PM Feature #3277: implement call-graph v3
- Interesting article on using the later Tinkerpop with the older OrientDB:
https://christinemdraper.wordpress.com/2... - 04:09 PM Feature #3277: implement call-graph v3
- Having a mechanism for Object to Graph Mapping (OGM) seems useful. Unfortunately, the existing solutions are relativ...
- 04:05 PM Feature #3277: implement call-graph v3
- Something that makes me concerned about OrientDB:
http://orientdbleaks.blogspot.com/2016/06/one-year-of-orientdb-l... - 01:27 PM Feature #3277: implement call-graph v3
- Greg Shah wrote:
> My sense is that OrientDB may be the better solution. There are two concerns:
>
> * It will t... - 12:27 PM Feature #3277: implement call-graph v3
- Greg, a good read is the documentation in callgraph/callgraph_lib.rules - it documents all the call sites which are i...
- 11:37 AM Feature #3277: implement call-graph v3
- Interesting D3 samples:
http://vowl.visualdataweb.org/webvowl/ (very close, code is at https://github.com/VisualDa... - 11:34 AM Feature #3277: implement call-graph v3
- One question I am considering is whether we should move to a newer graph database implementation. It seems like the ...
- 10:35 AM Feature #3277: implement call-graph v3
- Constantin: I am refreshing my understanding of the current implementation. As I dig into the code, it would be very...
- 10:32 AM Feature #3277: implement call-graph v3
- This work is intended to provide a web UI to display and explore a more complete version of the call graph.
+Objec...
04/19/2017
04/18/2017
- 06:26 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Rebased task branch @1521c@ from P2J trunk revision @11148@. New revision is @11152@.
- 12:53 PM Feature #1514: implement fully dynamic reports (backed by the database)
- Branch 1514a was rebased from trunk rev 11147.
04/17/2017
- 06:05 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Rebased task branch @1521c@ from P2J trunk revision @11147@. New revision is @11151@.
- 01:46 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521c@ for review updated to revision @11150@.
All changes for only @gaps/expressions.rule@. This upd...
04/12/2017
- 04:49 PM Feature #1514: implement fully dynamic reports (backed by the database)
- A few notes about the RPC. While I agree with Greg that the REST-like programming model isn't a good fit, I think we ...
- 11:59 AM Feature #1514: implement fully dynamic reports (backed by the database)
- The objective for this task is to create a Java-based reporting engine that has an embedded web server (leveraging Je...
Also available in: Atom