I'm trying to set up Perforce integration in IntelliJ IDEA 10.5.2. There is a field named "Client" that doesn't make sense to me. I get the message "Connection problems: Client Unknown" whatever I type into the field. What should I enter into that field?
You need to enter the name of your Perforce workspace.
If you have set up the command line tool correctly you may run p4 set P4CLIENT on the command-line.
If you use the P4V GUI tool, the workspace name is easily found.
Open P4V and connect. On the top left, above everything, there are your:
[client], [port], [user] - Perforce P4V
They often look something like:
[client] ~ [your-name]_[random-letters-and-numbers]
[port] ~ [url]:[number]
[user] ~ [your-name]
Enter them in IntelliJ and press Apply.
Edit:
If you only see
[port], [user] - Perforce P4V
you need to go to Connection -> New workspace... and create a workspace.
You need to enter the local Workspace name into the dialog in Webstorm Options / Preferences to integrate it with Perforce.
In P4V, you can find this by looking at View > Workspace Tree, and then selecting the workspace you are trying to integrate.
Background: I'm setting up Perforce with Webstorm v2016.1 just now. I tried using the name of the workspace stream on the server at first, which kept giving me a "Client Unknown" error. This fixed the issue and allowed the connection to go through.
http://www.perforce.com/perforce/doc.current/manuals/intro/index.html before you go any further. Always start by reading the docs, you'll be a lot happier.
Related
I've run into this serious error while committing, and created a bug report.
I keep getting this error on TortoiseGit operations:
git did not exit cleanly (exit code 128)
I've reinstalled the program, rebooted, and tried to clone a fresh repo from github - nothing seems to work. I also deleted %appdata%\Tortoise git folder ... I'm at a loss now. Any advice on how to proceed?
It's probably because your SSH key has been removed/revoked. Make a new one and add it to your GitHub account.
for me I simply had to add configure my git username and email with the following commands:
git config --global user.email "you#example.com"
git config --global user.name "Your Name"
If you're running windows 7:
I was trying to decide the best way to do this securely, but the lazy way is :
right-click the parent folder
click the "properties" button
click the "security" tab
click the "edit" button
click the group that starts with "Users"
click the checkbox that says "full control"
click all the OK's to close the dialogs.
I realize this might circumvent windows "security" features, but it gets the job done.
git-bash reports
fatal: Unable to create <Path to git repo>/.git/index.lock: File exists.
Deleting index.lock makes the error go away.
In my case a folder in my directory named as the git-repository on the server caused the failure.
Deleting index.lock worked for me
on win7 64:
git-gui gives a good answer: a previous git has crashed and left a lock file. Manually remove.
In my case, this was in .git/ref/heads/branchname.lock.
delete, and error 128 goes away. It surprises that tortoisegit doesn't give such an easy explanation.
In my case, it was because of the proxy. A proxy was needed in the corporate network and TortoiseGit / Git does not seems to automatically get information from Windows internet settings. Setting up the proxy address solved the issue.
For me, I tried to check out a SVN-project with TortoiseGit. It worked fine if I used TortoiseSVN though. (May seem obvious, but newcomers may stumble on this one)
In my case, I forgot to add git to the respository name at the end.
I did git revert a multiple times ,and it worked for me make sure un-check the files while reverting you need changes. Stash your changes and pull again.
I was having this same issue and I resolved it in the following way...
I have the NVIDIA "Tegra Android Development Pack" installed and it seems to also have a version of mysysgit.exe with it. TortoiseGit automatically found that installation location (instead of the standard git installation) and auto-populated it in the settings menu.
To correct this, go to: "Settings -> General" and there is a field for the path to mysysgit.exe. Make sure this is pointing to the correct installation.
An quick solution would be to create a new local directory for example c:\git_2014, In this directory rightklick and choose Git Clone
make sure the username and email fields are not empty in the config file. and try to clone to an empty directory. these steps worked for me.
although, it is a very old thread, recently I got this error, and in my case, the link was broken. When the link to GitHub was fixed, it worked.
What has worked for me:
Removing all offending branch related files from all folders in .git\ref and .git\logs
I have latest version of phpstorm, downloaded today. While uploading files to remote server i click on refresh icon in remote host, then phpstorm displays error
could not list the contents of folder phpstorm. How can i correct that ??
Go to Tools -> Deployment -> Configuration -> Advanced Options. Check Always use LIST command.
Works like a magic!
Go to Tools > Deployment > Configuration > Advanced Options and Select the Pasive mode option.
It worked out for me!
For me was that for some reason the folder of the Root path was deleted. Check yours!
for me nether of these settings worked. in my settings i didn't even have passive mode (intellij idea).
so what i did is, lookup the server directory with a php info file (uploaded it with another ftp tool, that was able to list the direcories: transmit) and then rebuild that path inside tools / deployment / root path.
Go to Tools > Deployment > Configuration > Connection > Advanced and select:
Passive mode
Compatible with old version of listining children
Instead of MLSD
It worked out for me!
Step by step image
I don't know, how that happened but before today I could right click on any folder and there would be and an option Git Bash here. But today I dont have that option. Anyone knows how to get that back?
HOW TO FIX WITHOUT RE-Installing:
I got this problem after moving all my programs off of my main hard drive and pasting them into my "P" drive. But kept all of the directory structures the same.
Git was moved from:
C:\DEV\PROG\GIT
TO:
P:\DEV\PROG\GIT
1: Open The Registry Editor:
Type "regedit" in start menu search and hit enter.
2: Find the context menu shortcut configuration for "git bash here"
In regedit: Menu "Edit" > "Find" > "Find what" and enter "git_shell"
3: Edit the Data value so that path points to the correct location.
In my case I changed:
"C:\DEV\PROG\GIT\git-bash.exe" "--cd=%v."
TO:
"P:\DEV\PROG\GIT\git-bash.exe" "--cd=%v."
Screen shot included below.
Steps if you can't use the reinstall metod.
Use REGEDIT
1/ Open regedit (search it if needed)
2/ Go to 'HKEY_CURRENT_USER/Software/Classes/Directory/Background'
3/ Create new key 'shell'
4/ Create new key 'Git bash here' (or whatever name you want to see in the menu)
5/ Create new key 'command' (must be named command)
At this point point you'll have
'HKEY_CURRENT_USER/Software/Directory/Background/shell/Git bash here/command'
6/ Edit the value of the command key as follow 'pathToGit/git-bash.exe'
Update or open new windows explorer and you'll see it when right clicking.
Image to sum this up :
Reinstall Git and select:
Context menu entries: "Git Bash Here" (and the "Git GUI Here" option)
During the installation. Can't say why it disappeared, but this should bring it back.
Run this script (AddGitToExplorerContextMenu.reg).
You may need to update the location of Git. You can add it
manually through regedit also
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Directory\Background\shell\git_shell]
#="Git Bash"
[HKEY_CLASSES_ROOT\Directory\Background\shell\git_shell\command]
#="\"C:\\Program Files\\Git\\git-bash.exe\" \"--cd=%v.\""
Had the same issue , realized that previously right clicking anywhere or inside the folder the Option would show but now I had to select or highlight the folder and then right_click for the option to show.
Uninstall Git completely and delete the Git folder in program files.
Install Git.
From the Context menu, select "Git Bash" & "Git GUI here" options.
I found what I was looking for was in the left pane, not in the right folder. And still using the right-click.
Press SHIFT+F10. It will appear
After Windows 11 update, it got invisible. I first uninstalled the older version and installed the latest 2.35 version. it was still not visible.
It is still there albeit inside another folder in the context menu that comes with a right click.
By going inside any folder right-click INSIDE that folder, in German OS there is
Shift + F10 combination you have it there like before. Or without this shortcut combination go inside Further option (This last) it is there.
It worked fine when I was using Win 10 ,after upgrading my windows to 11 it stopped working.
I solved my problem by following these simple steps.
Uninstall Git completely on computer
Download it here : https://git-scm.com/download/win
Install it
It works fine now!!!
Once you right click on the folder , click on 'Show More Options'.
Now you should be able to see all the earlier options such as 'Git Bash Here'
I have a thesis project that requires a project log to be submitted along with my final paper. As part of that log I'd like to include the Bazaar revision log and all the messages that it contains but I'll need to have them in a printable format.
I was unable to find any export feature in the Bazaar Explorer tool but I hope it's still possible to do somehow. Any thoughts?
Thanks!
You can get log in the text format using command-line: bzr log > log.txt or via Bazaar Explorer with running All Commands dialog and select log command there and then copy the log from status window. Read the help for log command to find the appropriate options. You may want to use -n0 option and maybe --forward one.
For completeness, you can use the bzr-xmloutput plugin to get an xml version and then process that into exactly what you want.
I've created a dtsx package with Sql Server Business Intelligence Development studio, and I am executing it using the dtexec utility. Using dtexec I am setting certain properties at runtime using the /set switch. So my command looks something like:
dtexec /f "mypackage.dtsx" /set
\Package.Connections[Destination].Properties[UserName];myUserName
This works perfectly when I run it on my local system (the one it was developed on). Unfortunately, when I copy this package to a different system and attempt to run this exact same command, I receive the following error:
Warning: The package path referenced an object that could not be found:
\Package.Connections[Destination].Properties[UserName]. This occurs when an
attempt is made to resolve a package path to an object that cannot not be found.
The new system that the package was moved to has SSIS installed and is running the same version of Sql Server as my local system (SP2). Maybe I'm misunderstanding something about the intended use of dtsx packages, but I really don't see how/why this is happening.
This steps is for creating an XML configuration file (.dtsConfig) which can keep your sensitive data, like the password of your connection string, without having a Protection Level that can make you difficult to move the package from one machine to another.
In this example, assumed you have an OLE DB Connection to an SQL database called MyDb.
Control Flow, Property: set "ProtectionLevel" to "DontSaveSensitive"
Control Flow, right-click empty space to get menu: click "Package Configuration"
Package Configuration Organizer: tick "Enable package configuration"; click "Add"
Package Configuration Wizard, Select Configuration Type: set "Configuration type" to "XML configuration file"; choose "Specify configuration directly" radio button; click "Browse..."
Select Configuration File Location, fill "Filename": [PackageName].dtsConfig (easy if same folder and same filename as the package itself, just different extension); click "Save"
Package Configuration Wizard, Select Configuration Type: click "Next >"
Package Configuration Wizard, Select Properties to Export: traverse the following tree nodes and tick its checkbox; click "Next >"
\[PackageName]\Connection Managers\MyDb\Properties\Connection String
\[PackageName]\Connection Managers\MyDb\Properties\Password
Package Configuration Wizard, Completing Wizard, click "Finish"
Package Configuration Organizer: click "Close"
Solution Explorer: right click the root tree for menu, click "Add", "Existing Item...", click [PackageName].dtsConfig, click "Add"
Solution Explorer: double click \Miscellaneous\[PackageName].dtsConfig to load into editor;
Main menu: click "Edit", click "Advanced", click "Format Document"
Traverse the XML tree node: \DTSConfiguration\Configuration[Path="\Package.Connections[MyDb].Properties[Password]"]\ConfiguredValue; key in the database password; save the file
Windows Explorer: navigate and double click [PackageName].dtsx
Execute Package Utility, Configuration, click "Add", double click [PackageName].dtsConfig, click "Execute"
When required to move the .dtsx to another machine, simply accompany it with its .dtsConfig. Hope this helps.
Cheers, Ari.
You'll need to create a deployment utility if you;re moving the package between machines. Your connection information gets encrypted using a key specific to your machine.
If you go to the project properties in VS, Select the deployment utility section and set the CreateDeploymentUtility option to true. This will create the deployment utility in the bin folder, you can then copy all that to the new machine, run the installer, and all should work fine.
The quickest way to move packages between machines and avoid all the signing of the packages is the following.
In Visual Studio with the package open select "Save copy of PackageName" As
You then get a wizard up. Easiest one is probably to just select file store. Then at the base of the wizard you will see protection level. Select Encrypt Sensitive data with a password. Enter a password.
On the server you wish to move it to select Import Package and it will prompt you for the password. Enter it and your connection information will be correctly move to the new server.
Definitely not best practice but it is a good method for quickly moving things around test servers.
On your control flow properties, there is a property called "ProtectionLevel". If you set this to 'DontSaveSensitive' then that might cause you less headaches while doing dev and testing. For production scenarios where security is a requirement then you might need to find another solution.
Here are the guidelines from MSDN about package security. Setting the Protection Level of Packages