Re: [topbraid-users] TBCME 6.4 crashes in SPINMap Diagram

[Jack Hodges]

I found an error log in the TBCME package under 
Contents/MacOS/hs_err_pid48983 if that is what you are referring to. 
Attached. This is only happening with regularity in the SPIN Map diagram 
editor and usually when I try to save a snapshot. So I started editing in 
raw.

Can I run a python script in SPARQL MOTION? If so maybe I can use rdflib to 
convert the data.

On Wednesday, May 19, 2021 at 2:42:39 PM UTC-7 Holger Knublauch wrote:

>
> On 2021-05-20 7:30 am, Jack Hodges wrote:
>
> I have been having stability issues with TBCME 6.4 where it crashes 
> several times a day, but I began a SPINMap project yesterday and it is 
> hanging every 15-30 seconds, requiring me blast the process. I would use 
> TBCME 7.0 but I have been having issues with even starting that one so I am 
> reluctant to move operations over to it. Is this stability problem fixed in 
> 7.0?
>
> I doubt it, because nothing related to SPINMap has been touched for a 
> while, and TBC 7.0 is not much different from 6.4 feature-wise. It would 
> help us better understand the crashes if you could send the Eclipse error 
> log with Exception stack traces. I don't know what to do with the other 
> file you have sent.
>
> Holger
>
>
> It would be worth the switch if I can do something that should take 
> minutes in less than a day. Sorry to be whiner. 
>
> Jack
>
> Macbook Pro 2018
> 2.6 GHz 6-core Intel Core i7
> 32 GB 2400 MHz DDR4 memory
> macOS Big Sur, version 11.3.1
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TopBraid Suite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to topbraid-user...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/topbraid-users/c49d356e-e5b2-4313-b9e2-0fb33d65976dn%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/b4828643-0a2b-410d-8731-b8ff17ec7910n%40googlegroups.com.
{\rtf1\ansi\ansicpg1252\cocoartf2580
\cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fmodern\fcharset0 Courier;}
{\colortbl;\red255\green255\blue255;\red0\green0\blue0;}
{\*\expandedcolortbl;;\cssrgb\c0\c0\c0;}
\margl1440\margr1440\vieww11520\viewh8400\viewkind0
\deftab720
\pard\pardeftab720\partightenfactor0

\f0\fs24 \cf2 \expnd0\expndtw0\kerning0
\outl0\strokewidth0 \strokec2 #\
# A fatal error has been detected by the Java Runtime Environment:\
#\
#  SIGSEGV (0xb) at pc=0x7fff2037f81d, pid=48983, tid=0x0103\
#\
# JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build 1.8.0_222-b10)\
# Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode bsd-amd64 compressed oops)\
# Problematic frame:\
# C  [libobjc.A.dylib+0x681d]  objc_msgSend+0x1d\
#\
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again\
#\
# If you would like to submit a bug report, please visit:\
#   http://bugreport.java.com/bugreport/crash.jsp\
# The crash happened outside the Java Virtual Machine in native code.\
# See problematic frame for where to report the bug.\
#\
\
---  T H R E A D  ---\
\
Current thread (0x00010182d000):  JavaThread "main" [_thread_in_native, id=259, stack(0x7ffeef40,0x7ffeefc0)]\
\
siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x1aeb5d20\
\
Registers:\
RAX=0x0001aeb487d0, RBX=0x7ffeefbfb708, RCX=0x62604060, RDX=0x60f11350\
RSP=0x7ffeefbfb6b8, RBP=0x7ffeefbfb6c0, RSI=0x7fff7ba6911d, RDI=0x0001aeb487d0\
R8 =0x0001aeb487d0, R9 =0x, R10=0x1aeb5d08, R11=0x7fff7ba6911d\
R12=0x1000, R13=0x60f11350, R14=0x60ede6a0, R15=0x\
RIP=0x7fff2037f81d, EFLAGS=0x00010202, ERR=0x0004\
  TRAPNO=0x000e\
\
Top of Stack: (sp=0x7ffeefbfb6b8)\
0x7ffeefbfb6b8:   7fff205d021d 7ffeefbfb6e0\
0x7ffeefbfb6c8:   7fff2066bc7c 0001aeb487d0\
0x7ffeefbfb6d8:   7ffeefbfb7b8 7ffeefbfb790\
0x7ffeefbfb6e8:   7fff2066bbfa 62604060\
0x7ffeefbfb6f8:   0001aeb487d0 000b\
0x7ffeefbfb708:   7fff807d8340 c200\
0x7ffeefbfb718:   7fff2066bc4b 7fff8098c698\
0x7ffeefbfb728:   60ede6a0 60f11350\
0x7ffeefbfb738:   62604060 041d0174\
0x7ffeefbfb748:   1000 0001aeb487d0\
0x7ffeefbfb758:   7fff801e5400 5d964d592cb40058\
0x00

Re: [topbraid-users] Content tag set - tag display fails

[robatki...@gmail.com]

I upgraded to 7.02 and I get a similar error:

Invalid SPARQL query string: Line 5, column 34: Unresolved prefixed name: 
tagger:defaultTagProperty

tagger prefix is set, and this property is set for the graph 

and the query works in the SPARQL pane (with or without the Graph clause) :

SELECT DISTINCT ?predicate ?predicateLabel ?object ?subjectRootClass 
?labelGraph 
WHERE { GRAPH 

 
{
{
{
?any tagger:defaultTagProperty ?predicate .
}
UNION
{
?any tagger:tagProperty ?predicate .
} .
} .

?subject ?predicate ?object.
BIND(spl:object(?taggerGraph, tagger:subjectRootClass) 
as ?subjectRootClass) .
BIND 
(swa:propertyLabelAtClassOrShapeInGraph(?predicate, ?subjectRootClass, 
?labelGraph) AS ?predicateLabel) .
}
}

so i think the issue is not the old code but something about the graph 
closure logic .. 

On Friday, 21 May 2021 at 00:42:00 UTC+10 Richard Cyganiak wrote:

>
> Hi Rob,
>
> On Thu, 20 May 2021 at 01:23, robatki...@gmail.com  
> wrote:
>
>> Interesting - a brand new workspace created with 6.4 ... 
>>
>> and I _do_ find this code in that js file...  
>>
>> Version: 6.4.0.v20200617-1843B
>>
>
> That's the 6.4.0 beta.
>  
>
>> notwithstanding,  the question about why it fails when I create the 
>> tagset programmatically instead of vi the UI still stands.  
>>
>
> Using the 6.4.0 release version should resolve the issue.
>
> Richard
>
>
>  
>
>>
>> I can inspect the transitive import tree of the graph I created vs the UI 
>> created one, but the actual query goes against a rdfex.org closure built 
>> using logic I can't access  - so is there a simple way to test queries 
>> independently against this? 
>>
>> I guess I can post queries matching the failed call to inspect that 
>> graph's import closure - but that depends on how it was achieved in the 
>> back end - maybe it doesnt report it ?
>>
>> Is there perhaps a SHACL shape I can use to validate that all the 
>> metadata needed to work as a tag set is correct? (PS - this would be a very 
>> helpful developer tool set of all the hidden contracts about metadata :-) )
>>
>> On Wednesday, 19 May 2021 at 22:20:44 UTC+10 Richard Cyganiak wrote:
>>
>>> This function was never called from Java code, but it was called from 
>>> JavaScript front-end code via the SPARQL endpoint in 6.3.x. These calls 
>>> were removed in 6.4.
>>>
>>> The call was in the workspace file 
>>> teamwork.topbraidlive.org/ui/teamwork.www/build/taggerApp.bundle.js . 
>>> In a 6.3 workspace, that file will contain the string 
>>> currentContentRootClass. In a 6.4 workspace, it should not.
>>>
>>> An undefined function in SPARQL is not an error, but is treated as an 
>>> unbound value. So, if it's in a FILTER, the filter is treated as false, and 
>>> if it's in a BIND, no value will be bound. This is a (mis?)feature of the 
>>> SPARQL standard in general: Almost any query that matches the SPARQL 
>>> grammar will evaluate without error. At worst it will produce no results.
>>>
>>> Richard
>>>
>>>
>>>
>>> On 19 May 2021, at 05:50, robatki...@gmail.com  
>>> wrote:
>>>
>>>
>>> version 6.4, and its a new workspace built under there.  I also searched 
>>> but couldnt find it - yet network sniffing showed it being called... so I'm 
>>> guessing its in Java code somewhere..
>>>
>>> Given i can make it work, with just a warning, there must still be 
>>> something else not quite right - I replicated the imports, metadata, 
>>> namespaces etc from the CreateTaggerProjectService and AFIACT it works 
>>> exactly as expected except this one glitch..
>>>
>>> On Wednesday, 19 May 2021 at 12:44:06 UTC+10 Holger Knublauch wrote:
>>>
 Hi Rob,

 I cannot find the string currentContentRootClass anymore in our code 
 base, yet I can see it was used in some older versions of 
 taggerprojects.ui.ttlx last year. Is there a mismatch between your 
 workspace and the version of the UI code? What version are you on?

 Holger


 On 2021-05-18 11:00 pm, robatki...@gmail.com wrote:


 If I use the UI to create a tagset, when I display a tagged property 
 the error log shows a warning:

 URI  
  has no 
 registered function factory

 when I try to programmitically recreate the tagset, even though all 
 metadata looks the same, all namespaces look the same it behaves 
 differently - and the tag display call fails with:

 *Invalid SPARQL query string: Line 3, column 78: Unresolved prefixed 
 name: tagger:currentContentRootClass.*

 and the tag doesnt display..

 I cant find thi