Page MenuHomeSoftware Heritage

Add low level API (WIP)

Authored by seirl on Oct 2 2019, 7:34 PM.

Diff Detail

rDGRPH Graph service
No Linters Available
No Unit Test Coverage
Build Status
Buildable 8154
Build 11751: tox-on-jenkinsJenkins
Build 11750: arc lint + arc unit

Event Timeline

seirl created this revision.Oct 2 2019, 7:34 PM
seirl updated this revision to Diff 6951.Oct 2 2019, 7:42 PM

typo fixes

seirl updated this revision to Diff 6956.Oct 4 2019, 2:58 PM
  • rebase
  • add 'deep' methods
seirl updated this revision to Diff 6962.Oct 4 2019, 5:20 PM

Fix stderr

seirl updated this revision to Diff 6963.Oct 4 2019, 5:23 PM

Refactor simple_traversal

This revision was not accepted when it landed; it landed in state Needs Review.Oct 4 2019, 6:25 PM
This revision was automatically updated to reflect the committed changes.
seirl reopened this revision.Oct 4 2019, 6:28 PM
seirl updated this revision to Diff 6968.Oct 4 2019, 6:28 PM
  • backend: propagate java errors to the toplevel
zack requested changes to this revision.Oct 6 2019, 11:41 AM
zack added a subscriber: zack.
zack added inline comments.

why the explicit timeout here?
can't this fail for the wrong reason, e.g., when calling the leaves method on large graphs?


this looks graphviz-specific, so it should go in instead


It's not clear to me why the first argument is called "parent_graph" (here, and everywhere in the module). Isn't it just the graph the various visitors are working on?

This revision now requires changes to proceed.Oct 6 2019, 11:41 AM
zack added a comment.EditedOct 6 2019, 11:42 AM

btw, I've tested this diff manually in tox and it does build fine

seirl added inline comments.Oct 6 2019, 11:54 AM

I'm gonna add a comment for the timeout.

No, this is only for opening the FIFO, not reading it, so it can't fail like that. The FIFO is opened on both sides at the beginning.

The problem is, if there is an exception in the java call thread and the FIFO is never created, this thread will block endlessly without timeout, because the FIFO has to be opened from both sides for the open(2) call to return. Adding a timeout for this open() call allows Java exceptions that happen between the Java call and the open() on the Java side to be propagated to the main thread.

seirl updated this revision to Diff 6987.Oct 7 2019, 5:49 PM
  • rebase
  • graph: cosmetic fixes and comments
zack accepted this revision.Oct 7 2019, 8:25 PM
This revision is now accepted and ready to land.Oct 7 2019, 8:25 PM
seirl closed this revision.Oct 8 2019, 1:26 PM