In 0.9.0, multiple false errors

Bug Reports Editor
,
1

I performed a clean installation of SysIDE, making sure that .sysml-2ls and .vscode were clean of SysIDE elements first.

I have a simple .sysml file with the following notation:

part thisPart;

The following errors occur:
Could not find implicit specialization for Subsetting ‘Parts::parts’
Could not find implicit usage specialization for PartUsage ‘Parts::parts’
A Feature must be typed by at least one type.
At least one of the itemDefinitions of a PartUsage must be a PartDefinition.

2

Hi flammafeuer,

This is a known issue with SysIDE Editor, as documented here: docs/known_limitations.md · main · Sensmetry / public / SysIDE Editor · GitLab

It is a very unfortunate bug with Editor and the technology stack it uses. We could not find a reproducible way to recreate this issue on any of our machines, which prevents us from finding the root cause of the bug. Therefore, we are looking for community to step in here and help out with fixing this issue. If you are proficient with TypeScript, we would be very grateful if you could try and find the root cause.

Other possible steps you could take are:

  • double-check that you have NOT set the syside.editor.standardLibraryPath setting in your User Settings JSON and delete it if you have it set
  • if that still does not help, you could try using SysIDE in your web browser through https://vscode.dev/
  • if that still does not help, you could join the Early Adopters Program of SysIDE Pro through the SysIDE website. The Pro version is built on a totally different technology stack and does not have this error.
2 Likes
3

Thanks Simonas, I don’t have much experience with TypeScript, but I’d be
happy to see what I could uncover. Do you have advice on where to start,
which files would need to be looked at?

4

Hi flammafeuer,

One place to start is packages/syside-languageserver/src/services/shared/workspace/workspace-manager.ts where SysMLWorkspaceManager.loadAdditionalDocuments does the loading of the standard library.

There is also packages/syside-languageserver/src/services/shared/workspace/metamodel-builder.ts where there are a lot of different functions for adding implicit subtypes, but they all use SysMLMetamodelBuilder.findLibraryElement which seems to be where the errors are coming from.

It would be much appreciated if we could find out where in the chain things fail to load.

1 Like
5

I just requested access to the early adopters programme

1 Like
6

@Hormo Hi, thanks. I reached out to you via email with details on the program.

7

Hello everyone. I am not sure that this is the same issue, but since I have updated the SysIDE editor, lot of errors appears in the editor. For instance, after launching the Excel2Requirements python example, there are lot of errors in the resulting file (see image below). The error is:

“Could not find implicit specialization for Subclassification 'Requirements::RequirementCheck’sysml
Could not find implicit definition specialization for RequirementDefinition 'Requirements::RequirementCheck’sysml”

In addition, even the sysml.library seems to contains errors

image
image1075×568 30.1 KB

Thank you for your help.

8

@jm.gauthier Thank you for reaching out.

We are aware of the problems with requirement in SysIDE Editor, but based on our resource prioritization the current focus has been on the Professional tools. Unfortunately, this has led to a temporary hold on open-source development and relying more on community suggested solutions. This is because the Editor has a completely different architecture and codebase from our professional tools, requiring separate development efforts.

We are currently working on leveraging the capabilities of the professional tool suite to bring syntax highlighting and semantic validation to Modeler. An early version of this will be available to Early Adopters Program next week. It is stable and does not have these errors.