Accidentally i deleted a notebook from my databricks repo before any commit, I expected to restore it from trash folder but the notebook is not there. Is posible to restore from any directory on the server or something like that?
If you right click on the repo it should show the following context_menu:
.
Clicking on git will lead you to your latest changes, making it possible to revert uncommitted changes.
It was never versioned. I just had created a notebook then deleted it by mistake so it was never anywhere but my repo workspace. Once I deleted the notebook I was hoping to find it in my trash folder, but aparently there is no way no restore it.
Related
I just reverted some changes in files. These changes were not staged or commited.
Is there anything I can do?
thanks!
There's not much you can do to recover your changes.
If you are using Intelli as your IDE there is a "local history" you can access be right clicking on a file in the project view.
So our project has been using Azure Data Factory with GIT integration for about a year without issues.
We just encountered one I need help with.
The data factory pulls in its changes from GIT. So usually we just check in / merge branches, and then I go to the portal and press publish new changes and it works fine.
Everything looked normal, but this time it failed because there was a pipeline referencing a deleted dataset.
https://i.imgur.com/FuJ6wOc.png
I looked but couldn't find the pipeline in the project or my git repo's json files.
Finally I realized there was this button to switch over to "DataFactory" mode. I assume this was the old mode we used before we set up GIT?
https://i.imgur.com/J2lQmYY.png
In this mode I found the pipeline that was causing the failure, deleted it, but then I can't actually save the delete because I am not allowed to publish from Data Factory mode with GIT sync enabled.
https://i.imgur.com/B4Q4k2C.png
So I seem to be in a holding pattern, can't publish from GIT to deploy code due to DataFactory mode, yet I can't fix DataFactory mode because I have GIT enabled.
I suppose I could disable the GIT sync, fix the DF mode, and renable the git sync but I am worried that might break something else.
Anyone seen this before?
Thanks
I looked but couldn't find the pipeline in the project or my git
repo's json files.
In this mode I found the pipeline that was causing the failure,
deleted it, but then I can't actually save the delete because I am not
allowed to publish from Data Factory mode with GIT sync enabled.
It seems your data between Git mode and Data Factory mode isn't synchronize. You can try to import existing resources to repository.
I suppose I could disable the GIT sync, fix the DF mode, and renable
the git sync.
I think this way can work and it won't break something else.
You can disconnect the GIT repository, delete the pipeline from data factory mode, publish and re-connect to GIT. Make sure to import the existing resources to repo when you reconnect with GIT.
As described in the header, I lost a hard drive that had a tortoise repository on it, but I managed to recover the files folder from that drive, unfortunately without the repository.
In the meantime the recovered folder now has a "!" icon on it, and I can't do anything with it (clean up, relocate, check in) since it says that it can't find its old repository.
Is there any way to move it to an existing repository on the new drive, or even just create a new one?
Thanks!
Cleanup doesn't require access to the repository. If even cleanup fails, then your backup wasn't complete or completely successful because the working copy is broken.
If you lost the repository, then you have to start from scratch (now you know why backups are important). Since you still have the files from your working copy, copy them to the new drive, then remove all hidden .svn folders. After that, you can import those files in a fresh repository.
In subversion I'm trying to commit a project but running into an issue.
The error I get is
Illegal repository URL ''
How come I can run update, but commit on the same tree shows that?
Try this, it worked for me:
Create a folder.
Right button over folder and create repo here.
When pop up appears select create folder structure and then open folder.
When repository browser appears you see tags branch etc, right button again and create folder but now with tool tortoise.
Update you file to folder.
After some hunting around it seems that a few other people have experienced some sort of local corruption at the top level their checked out project directory which is where I was committing from.
I followed the same procedure that was used to solve those cases which is to back up the sources. Check out the project again. Finally copy the changed files back over the freshly checked out copy. Check it builds correctly. And then commit that.
It seemed to solve it for me.
This has been plaguing me for a week.
SVN keeps telling me that a certain file "does not exist in repository".
Fine. Let's just delete it. Forget about it. Ignore it. Whatever. I don't really care about this file (especially if it continues to fail the nightly check-in).
The most bizarre part? A "restore" will actually RESTORE the file from the repository, so its there (corrupted, maybe?).
...and this has to be the icing on the cake. If I delete the file through Windows Explorer, SVN will RESTORE the file from the repository, and right after that state that it doesn't exist in the repository. WTF?
Does anyone have a clue how to get rid of this?
I've already tried clean-ups, reversions, deletions and anything else imaginable, but this one has me stumped.
Thanks for any tips you might have...
It seems most likely that you have corrupted your local working copy, e.g. by moving folders or some other manipulation that you did with windows explorer but should have done through the TortoiseSVN context menu. The information inside the .svn folders now no longer matches the state of the working copy, which is confusing Subversion.
To fix this, delete the parent folder ("Originals") in your working copy with windows explorer (NOT with TortoiseSVN). Then do a TortoiseSVN "update" at the root of your working copy. This should restore the folder in working order.
Another option is to discard your working copy entirely and do a fresh checkout.
Note that the next release of Subversion (1.7) will reduce the opportunities for corrupting your working copy by centralizing all metadata in a single .svn folder at the root.
I've had similar problems with corrupted working copies. Sometimes the working copies have a lot of pending changes but unable to checkin. To resolve this, I use the following approach (svn 1.7+):
Checkout a fresh working copy into a new directory (path2)
In the fresh working copy, if the offending file is there, delete it if needed.
Commit the fresh working copy
In the fresh working copy, delete everything except the .svn directory
Copy everything from the old working copy except the .svn directory into the fresh working copy.
Commit the fresh working copy again
Delete (or backup) the old working copy
Rename the fresh working to the old working copy (path2 to path)
I had faced a similar problem wherein i had a folder, for example "FolderA" which consistently shows in svn update even though I had deleted it.
It would not even show in the folder list but svn would still recognise it as if it exists.
I followed below steps:
1.Create same folder name for which svn was giving error in the same file location
2.Added it to svn checkout. Since it gave conflict errors, i resolved it using the svn option to resolve.
3.Deleted the folder and committed my svn.
Error was resolved