-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Method duplication exception after running **v up** (pref.c.v and pref.v) #21636
Comments
The problem is that in two files one called pref.c.v and pref.v, in the documentation it said that this file was renamed, but in v up it is not considering this action, generating this conflict. |
You somehow kept Either just delete that file and try again (hoping you don't have any other files that should've been deleted), or do a full re-install of V. There is an option to |
For this it would be important to have the user's space separated from the language itself and its resources, thus facilitating this update. Something like I did a clean install, because I didn't feel confident in simply deleting the file and restarting the process. |
Describe the bug
Being aware of version 0.4.6 I ran the v up command, but it returned an exception
Reproduction Steps
cristovao@cristovao-Predator-G3-572:~$ v -version
V 0.4.4 c9933da
cristovao@cristovao-Predator-G3-572:~$ v upgrade
Modules are up to date.
cristovao@cristovao-Predator-G3-572:~$ v up
Expected Behavior
Upgrade to 0.4.6 version
Current Behavior
Possible Solution
Apparently, just removing the duplicate method is_js
Additional Information/Context
No response
V version
0.4.4
Environment details (OS name and version, etc.)
Ubuntu 20.04.6 LTS 64-bit
Intel® Core™ i7-7700HQ CPU @ 2.80GHz × 8
NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] / Mesa Intel® HD Graphics 630 (KBL GT2)
Note
You can use the 👍 reaction to increase the issue's priority for developers.
Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.
The text was updated successfully, but these errors were encountered: