-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[README] [TUTORIAL] Error running dune build after changing paths #15
Comments
I think maybe it has something to do with these lines, which the coq-synthesis plugin doesn't do anything about: https://github.com/UCSD-PL/proverbot9001?tab=readme-ov-file#create-a-python-virtual-environment |
If I do that manually, and set the right environment, I now get this error instead:
|
Looks to be a problem with the setup script not sourcing the conda env despite the command to do so being there. And then the second error is because I used a different Python version when following Proverbot9001's instructions on this. After talking to Arpan, I am trying to manually source the conda env before running dune build, and if that works we will probably update the instructions to make this the default. |
Now I get this error:
|
Other projects that have similar errors point to the weights file being incorrect, so it would help to have a weights file to use that we know already works on someone else's computer, and see if that works. |
I tried pointing instead to this URL and it seems to be working now! Or at least, So I guess there are two fixes that should come out of this:
|
How long is |
I gave up since it didn't seem to be timing out. Trying to load something in an IDE to try instead, so I tried this line:
And it just tells me that file doesn't exist even though it obviously does. (Also I don't think that step should be necessary if the build is doing a proper plugin installation, so I'm curious why it is needed.) |
OK, I moved that to theories and now that command works, but I'd like to look into why it's needed at all. But |
Interestingly, I am getting error messages on the command line it looks like, even when it seems to be taking forever. Not sure what these mean, though:
Our updated TODO list now:
|
On the error above, Alex says:
I think what we are seeing is that we generally have a versioning issue, where we rely on a fork of Proverbot with dependencies that were up-to-date when you set everything up, but that now have gotten out of sync and are no longer compatible. So the build either fails or gives you something that doesn't work because of the version changes. We need to make sure that everything we pull in here is versioned appropriately. |
Ah, on this one, you already had a fix in your branch of Proverbot9001, but I wasn't on the latest commit of that since I'd first tried to install this a while ago. So, to update the TODO list:
|
OK now the
However on the command line, I get an extra error:
So that means our TODO list is now:
|
And it works!!! (Added my fix to 6 above, and updated 3 since now Test.v works---but only in the IDE.) Lots to do to update instructions and build files and so on to make this usable though. Especially since upstream changes will continue to break this. Now I will start to get it working on vscode as well, once I figure out how to get Coq working on VSCode, but if you can look at these 7 things in the meantime that'd be amazing. |
Pushed changed that address TODO numbers 1, 2 and 5. |
After running
make setup
and then changing the paths, when I try to rundune build
I get the following error I am not sure how to resolve:Any idea what may be causing this?
The text was updated successfully, but these errors were encountered: