fahrjo / ultimate-automizer-vscode Goto Github PK

Add some support for preparing the C files, e.g. by inlining #defines and combining several source files.

One should be able to stop running verification jobs. The backend offers an API to stop jobs, in STDOUT mode, the executable has to be killed

Show the spinning wheel in the status bar while waiting for Ultimate to finish.

As verification is in general rather expensive, it is unfortunate that it is triggered for every save. It would be nicer (in particular for the backend) if verification would only be triggered manually.

License needs to be checked!

Hey, this plugin is a great idea, thank you very much!

Are you aware that we just recently changed our web backend? The API is somewhat compatible, but you can have a look at it at https://ultimate.sopranium.de or read the meager info we currently provide at https://github.com/ultimate-pa/ultimate/tree/dev/trunk/source/WebBackend .

Settings for...

• using logfile vs. REST-API
• URL for REST-API

Currently, the behavior is quite different wether one uses the output of local executable of ultimate or the web interface. This should be unified for both options

• Syntax highlighting
• related information
• output text
• settings
• toolchain

Tested on (REST-API, direct stdout, Ultimate wrapped in Docker Container):

• MacOS (12.6.3)
• Linux (Debian 11)
• Windows 10

In that mode (enabled in workspace settings), also the last function call in the FailurePath should be highlighted in the source file and contain the error information. This is necessary due to the fact, that in case of THADS, the assertions are hidden in the library file and only the function call in the user space is under control of the user.