-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Given the various branches and fixes in KaTools, I tried checking if the current state of KaTools/master (v4.1-97-gb9248b7) and KaTIE/master ("V0.3", pinned & fetched an hour ago) can read the traces I already have. Unfortunately, I get:
$ KaTie -t trace.json -q testing_query.katie --output-dir testing_query
Evaluating queries: 1 simple and 0 complex
Fatal error: exception Stack overflowssed)
Raised by primitive operation at Stdlib__Hashtbl.find in file "hashtbl.ml", line 541, characters 9-23
Called from Kappa_terms__Instantiation.subst_map_concrete_agent in file "core/term/instantiation.ml", line 256, characters 9-13
Called from Kappa_terms__Instantiation.subst_map_site in file "core/term/instantiation.ml", line 260, characters 12-16
Called from Kappa_terms__Instantiation.subst_map2_agent_in_action in file "core/term/instantiation.ml", line 308, characters 16-38
Called from Stdlib__List.map in file "list.ml", line 92, characters 20-23
Called from Stdlib__List.map in file "list.ml", line 92, characters 32-39
[last line repeats 1018 times]
I believe the line about the overflow, got printed over the "nM events processed", hence the "overflowssed". Probably.
The testing simple query:
query 'test.csv'
match c:{ +b: bCat() }
return {
'c': time[c],
'i': agent_id{b}
}
Is this an issue with KaTIE, or KaTools? I.e. should I iterate over KaTools commits until I find one that doesn't error..?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels