Giter VIP home page Giter VIP logo

vscode-pvs's Introduction

VSCode-PVS: An Integrated Development Environment for the Prototype Verification System

version installs license chat

VSCode-PVS is a new integrated development environment for creating, evaluating and verifying PVS specifications. The environment redefines the way developers interact with PVS, and better aligns the PVS front-end to the functionalities provided by development environments used for programming languages such as C++ and Java.

Latest version

vscode-pvs-1.0.64

Publications

Documentation

Requirements

Installation instructions

VSCode-PVS can be installed from the Visual Studio Code Marketplace or from GitHub.

Note: When installing VSCode-PVS for the first time, the extension will check if PVS Allegro v7.1.0 is present on your system. If PVS Allegro is not present, VSCode-PVS will show a dialog and try to download and install PVS Allegro. Should the extension fail to download and install PVS Allegro, try to download and install PVS Allegro manually from https://pvs.csl.sri.com/. Should everything else fail, please report the problem on the PVS group on Google, we will help you out.

Automatic installation of VSCode-PVS from the Marketplace (recommended)

Manual installation of VSCode-PVS from GitHub

  1. Download the .vsix file of VSCode-PVS from github.
  2. Click on the Extensions icon in the Activity Bar
  3. Click on the ... menu in the title bar, and use Install from VSIX to select the downloaded .vsix file


Installation of PVS Allegro

If PVS Allegro is not already installed on your machine, VSCode-PVS will automatically download and install it. Should VSCode-PVS fail to download and install PVS Allegro, please try the following two steps:

  1. Download PVS Allegro v7.1.0 for MacOS or Linux
  2. Follow the installation instructions reported in the INSTALL file included in the downloaded PVS package.

Once PVS Allegro is installed on your machine, you can link up PVS and VSCode-PVS by indicating the location of the PVS executables in the VSCode-PVS settings.


Updating VSCode-PVS

VSCode-PVS will be automatically updated every time we publish a new release in the marketplace.

All settings and preferences will be maintained when installing a new release.

If you would like to perform manual updates, e.g., to try out pre-releases, you can download and install the .vsix files posted on the PVS google group.

Functionalities

The main functionalities provided by the environment are as follows:

  • Syntax highlighting: PVS keywords and library functions are automatically highlighted.

  • Autocompletion and code snippets: Tooltips suggesting function names and language keywords are automatically presented in the editor when placing the mouse over a symbol name. Code snippets are provided for frequent modeling blocks, e.g., if-then-else.

  • Hover information for symbol definitions: Hover boxes providing information about identifiers are automatically displayed when the user places the cursor over an identifier.

  • Go-to definition: Click on the name of the identifier while holding down the Ctrl key to jump to the location where the identifier is declared.

  • Live diagnostics: Parsing is automatically performed in the background, and errors are reported in-line in the editor. Problematic expressions are underlined with red wavy lines. Tooltips presenting the error details are shown when the user places the cursor over the wavy lines.

  • Workspace Explorer: Interactive tree view showing all theories in the current workspace, name and status of theorems and typecheck conditions.

  • Proof Explorer + Prover Console: Interactive tree view for viewing and editing the current proof. A prover console allows interaction with the theorem prover. Auto-completion is provided (using the TAB key) for prover commands, as well as access to the commands history.

  • Proof Mate: Interactive proof helper for suggesting proof commands, sketching proof attempts, and repairing broken proofs. Proof Mate provides a playground for copying, editing, and writing of proof sections without restriction, and during a live proof session.

  • Plot Executable Functions: Executable functions that return a list of real numbers can be rendered in a plot diagram (see examples in helloworld.pvs)

  • Search NASALib: Search definitions and theorems in NASALib, an extensive PVS library developed and maintained by the NASA Langley Formal Methods Team.

  • Prototype Builder: Build interactive visual prototypes to demonstrate the behavior of executable PVS specifications (see also pvsio-web prototype examples)


Structure

.
├── client                       // PVS Language Client (VSCode entry point)
│   └── src
│       ├── providers            // Client-side service providers
│       ├── views                // User interface components
│       ├── common               // Utility functions 
│       └── pvsLanguageClient.ts // PVS Language Client implementation
├── icons                        // PVS icons theme
├── package.json                 // The extension manifest
├── syntax                       // Syntax highlighting
├── LICENSES                     // NASA Open Source License Agreement
├── Makefile                     // Makefile for building a .vsix image from the source code
└── server                       // PVS Language Server
    └── src
        ├── providers                          // Server-side service providers
        │     ├── pvsCodeLensProvider.ts       // In-line actionable commands
        │     ├── pvsCompletionProvider.ts     // Auto-completion
        │     ├── pvsDefinitionProvider.ts     // Find definitions
        │     ├── pvsHoverProvider.ts          // Hover information 
        │     ├── pvsProofExplorer.ts          // Proof tree editor
        │     └── pvsPackageManager.ts         // Installation manager 
        ├── parser               // Parser grammar and scripts      
        ├── common               // Utility functions           
        ├── pvsCli.ts            // PVS Command Line Interface
        ├── pvsProcess.ts        // PVS process wrapper
        ├── pvsLisp.ts           // Lisp reader for parsing PVS responses
        └── pvsLanguageServer.ts // PVS Language Server implementation

Notices

Copyright

Copyright 2019 United States Government as represented by the Administrator of the National Aeronautics and Space Administration. All Rights Reserved.

Disclaimers

No Warranty: THE SUBJECT SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY WARRANTY OF ANY KIND, EITHER EXPRESSED, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY THAT THE SUBJECT SOFTWARE WILL CONFORM TO SPECIFICATIONS, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR FREEDOM FROM INFRINGEMENT, ANY WARRANTY THAT THE SUBJECT SOFTWARE WILL BE ERROR FREE, OR ANY WARRANTY THAT DOCUMENTATION, IF PROVIDED, WILL CONFORM TO THE SUBJECT SOFTWARE. THIS AGREEMENT DOES NOT, IN ANY MANNER, CONSTITUTE AN ENDORSEMENT BY GOVERNMENT AGENCY OR ANY PRIOR RECIPIENT OF ANY RESULTS, RESULTING DESIGNS, HARDWARE, SOFTWARE PRODUCTS OR ANY OTHER APPLICATIONS RESULTING FROM USE OF THE SUBJECT SOFTWARE. FURTHER, GOVERNMENT AGENCY DISCLAIMS ALL WARRANTIES AND LIABILITIES REGARDING THIRD-PARTY SOFTWARE, IF PRESENT IN THE ORIGINAL SOFTWARE, AND DISTRIBUTES IT "AS IS."

Waiver and Indemnity: RECIPIENT AGREES TO WAIVE ANY AND ALL CLAIMS AGAINST THE UNITED STATES GOVERNMENT, ITS CONTRACTORS AND SUBCONTRACTORS, AS WELL AS ANY PRIOR RECIPIENT. IF RECIPIENT'S USE OF THE SUBJECT SOFTWARE RESULTS IN ANY LIABILITIES, DEMANDS, DAMAGES, EXPENSES OR LOSSES ARISING FROM SUCH USE, INCLUDING ANY DAMAGES FROM PRODUCTS BASED ON, OR RESULTING FROM, RECIPIENT'S USE OF THE SUBJECT SOFTWARE, RECIPIENT SHALL INDEMNIFY AND HOLD HARMLESS THE UNITED STATES GOVERNMENT, ITS CONTRACTORS AND SUBCONTRACTORS, AS WELL AS ANY PRIOR RECIPIENT, TO THE EXTENT PERMITTED BY LAW. RECIPIENT'S SOLE REMEDY FOR ANY SUCH MATTER SHALL BE THE IMMEDIATE, UNILATERAL TERMINATION OF THIS AGREEMENT.

Contacts

vscode-pvs's People

Contributors

pmasci avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vscode-pvs's Issues

Plugin lists commented out code in the PVS workspace explorer, and tries to prove the commented out lemmas

I have a X.tccs file in my directory originating from a X.pvs file.
In the tccs file, which was automatically generated, I have

%% TCCs associated with theory [...]
%% This file was automatically generated by PVS, please **do not modify** by hand.
[...]: THEORY BEGIN

% The mapped-axiom TCC (at line 253, column 12) in decl nil for
	% term generated from IMPORTING 
	%  YYY
	%     {{ ... }}
	% IMP_[...]_TCC1: OBLIGATION
	%   EXISTS (x: [...]): TRUE
	  % untried
	  % IMP_[...]_TCC1: OBLIGATION
	%   EXISTS (x: [...]): TRUE

All of the lines above are commented out (except the line [...]: THEORY BEGIN); I assume it's just some information for the user. However, the PVS workspace explorer seems to look into those comments and list a tccs whose name is

% IMP_[...]_TCC1
(yes, the percent sign and the space seem to be part of the name string).
Then when trying to "play it" it fails with

Starting prover session for   % [...]_TCC1

Error: formula not found error
Additional details on the error can be inspected in the Output panel, on channel pvs-server.

and the Output panel doesn't show anything.
It looks to me like commented-out lines from the .tccs files should be ignored by whichever process is scanning the file to list the tccs in the PVS workspace explorer.

Feature request: WSL2 support

Environment:

  • Windows 10 21H1
  • WSL2 with Ubuntu 20.04.3 LTS
  • VS Code 1.62.2
  • Remote - WSL extension for VS Code
  • PVS 7.1.0, installed inside WSL2
  • PVS extension for VS Code, installed inside WSL2 by code --install-extension paolomasci.vscode-pvs (VSCode GUI currently provides no option of installing vscode-pvs outside the host)

When running from within WSL2, VSCode says "This extension is disabled in this workspace because it is defined to run in the Local Extension Host. Please install the extension locally to enable."

Not sure but it might be helpful to separate the front-end part of the IDE from the bindings with local pvs installations.

product icon theme contribution is not a real product icon theme

Product icon themes are a new feature that got final in the upcoming 1.53 release.

I saw that the pvs extension shows up in the list of available product icon themes:
image

However what the extension contributes is not a real product icon theme (just a file icon theme).
May I suggest to remove the contribution point again to not confuse users?

prover console refuses to take focus

The prover console sometimes refuses to take focus.
This may happen when switching between WebViews (e.g., from TreeViz to the prover console).

The problem might be related to this vscode bug: microsoft/vscode#116857

The workaround is to click on the label of the tab of the prover console, and then click in the prover console.

xterm-js-focus

Problem with propax

Hi all

I've started playing with the VSCODE for PVS. I'm mostly happy with it, but some things
that. can be proved with regular PVS (from emacs) don't get proved from VScdoe.
This is related to the (propax) rule.

Here's an example:

simple: THEORY
  BEGIN 
    test: LEMMA TRUE
  END simple

Then when I try to prove test, the session looks like this:

Starting new prover session for simple@test

Installing rewrite rule sets.singleton_rew (all instances)

test :

  ├───────
{1}   TRUE

 >> (propax)

No change on: (propax)
Error: Proof-command error



 >> (assert)

No change on: (assert)
Error: Proof-command error

Tutorial

Hello. Here are remarks about the tutorial:

type checking not responding issue on Mac VSCode-PVS

Hello,

I am a student working on a joint project using PVS, and encountered the following issue in type-checking step:

Environment:

Issue:

  • No matter which pvs file I type check, it always shows the message "Almost ready, please wait... (Typechecking [the pvs file path])" and sometimes "unable to connect to pvs server ...".

I have tried reboot and reinstall the PVS extension, and reinstall VSCode. Would it be likely that I forgot to do something?

Thank so much in advance.

Missing Dependency Notification on Vcode

I recently downloaded VCode and was asked to dowload a PVS then after choosing a location on my laptop for the PVS a notive pops up saying that my laptop is missing dependency. That vscode is typically ran on lynux and mac not on windows (which is my operating system). I checked to make sure I was running the latest version of vcode and Im pretty sure that I am, I even dowloaded the windows version, so I am unsure what exactly I am to do at this point. I have recently enrolled at Lambda and one of the platforms I have been asked to download and register with is vcode. The notice also said that if I continue to get the alert even after double checking the version I downloaded to report it to githib. So here I am.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.