platform issueshttps://gitlab.simantics.org/simantics/platform/-/issues2023-08-09T09:42:11Zhttps://gitlab.simantics.org/simantics/platform/-/issues/975Employ WatchService for listening to changes in external SCL module files2023-08-09T09:42:11ZTuukka LehtonenEmploy WatchService for listening to changes in external SCL module filesCurrently if one imports an external SCL module file into SCL Console, the module's contents are read once and compiled (pass or fail). If any changes are made to the SCL module on disk, the program will not pick these changes up until t...Currently if one imports an external SCL module file into SCL Console, the module's contents are read once and compiled (pass or fail). If any changes are made to the SCL module on disk, the program will not pick these changes up until the program is fully restarted.
I think it would be possible to use Java NIO WatchService to track external module files for changes and react upon them?Tuukka LehtonenTuukka Lehtonenhttps://gitlab.simantics.org/simantics/platform/-/issues/665Restricted SCL environment2021-01-04T15:57:15ZMarko LuukkainenRestricted SCL environmentCurrently several Simantics based applications use SCL scripts for customization.
Unfortunately, this is currently unsafe, because we do not have means to restrict th functions that uses can use. Here is an example from a certain produc...Currently several Simantics based applications use SCL scripts for customization.
Unfortunately, this is currently unsafe, because we do not have means to restrict th functions that uses can use. Here is an example from a certain product as a customizable transformation rule:
```
import "nn/Proteus/ExtractionRulesUtils/Common"
importJava "java.lang.System" where
exit :: Integer -> <Proc> ()
propertyRule :: PropertyRule
propertyRule = extract do
exit(-100)
```
Executing the above rule as part of a model transformation closes the Simantics DB instance (DOS attack).https://gitlab.simantics.org/simantics/platform/-/issues/459SCL compiler returns type errors for type "a"2023-01-13T18:21:58ZMarko LuukkainenSCL compiler returns type errors for type "a""a" is supposed to be *any* type, hence reporting `Expected <a> got ...` type errors is not valid behaviour."a" is supposed to be *any* type, hence reporting `Expected <a> got ...` type errors is not valid behaviour.Marko LuukkainenMarko Luukkainenhttps://gitlab.simantics.org/simantics/platform/-/issues/289Import statements for ontologies not refreshed when target of URI changes2019-12-19T12:29:19ZReino RuusuImport statements for ontologies not refreshed when target of URI changesWhen a database URI is used in an `import "..." as` statement in an SCL module, the resources referred to with point notation are not recalculated when the resource that the URI refers to is changed.
When a shared library is removed and...When a database URI is used in an `import "..." as` statement in an SCL module, the resources referred to with point notation are not recalculated when the resource that the URI refers to is changed.
When a shared library is removed and re-imported. SCL modules keep referring to the resource ids of the deleted shared library instead of the resources currently defined by the URIs, even if those modules are defined by the imported shared library itself.Hannu NiemistöHannu Niemistöhttps://gitlab.simantics.org/simantics/platform/-/issues/46SCL compiler EApply.inferType() endless loop2019-12-19T12:28:50ZJani SimomaaSCL compiler EApply.inferType() endless loopHannu NiemistöHannu Niemistö