[Clone Manager Professional 9.2
Melva Simons
I'm trying to clone the default conda environment in ArcGIS Pro. I've tried through Pro, and also through the python command prompt. I've tried reinstalling Pro, installing Pro in E: (in case permissions were an issue on C:), updating permissions of affected directories, added relevant paths to the environmental variables. It always fails the same way. This is on a remote Windows Server machine. I've been able to clone the default env using a local PC (with the python command prompt, not through ArcGIS Pro's settings).
So to tie up my earlier posts, and for the record I now have my issue fixed. I should also say I am working on a local machine and not a remote Windows environment as per the original post. I responded as it was the exact same error message.
While fixed, I'm still not particularly clear what the root cause is/was, and suspect there is still a problem lurking in the background. The history of community posts concerning failed and broken cloned environments, and the various hack-arounds, would suggest as much.
Thanks to the community for posting their various issues and work-arounds for what seems to be an ongoing and perpetual problem. It helped me distill from the collective wisdom and stumble across the solution above.
Like 3 different attempts later I finally cloned my environment after the upgrade from Pro 3.0 to 3.2. The first attempt was through the Pro Package Manager, but for reasons I'll never know it failed twice. The second time I followed the post from DanPatterson and used the python command prompt, but it didn't finish because of an SSL error.
The "partial-clone-copy-and-paste-hack" solution that worked for me is ... a hack. I'd still be interested in understanding what the root cause is, though. I switch ArcGIS Pro licenses between two devices and have not upgraded Pro on my other device as I don't want the environment on that device to fall into the same state.
Reading through the log files myself and @JoelMcKechnie provided, it looks like there was a write failure while running a post-link script for that particular package. For some reason, it can't find the source file or directory it needs to write and/or doesn't have permissions to write it. This doesn't make sense to me: we're cloning a working environment, so if the source environment doesn't have the file, you'd think the source environment shouldn't work either. I ran the clone command as Administrator, so there should be no write permission problems. This write issue is why I went the copy-paste route following failed clone attempt.
Maybe the way conda looks for packages is one avenue to explore as per this (old) Github Issues thread on post-link script errors? I can theoretically see how this could interfere with where conda looks for files during cloning. Could it be that where Anaconda, ESRI and jupyter are all at are not synced? Surely not...
I'm not overly familiar with how Anaconda as a package manager works, so lack the experience and context to guide and focus trouble shooting. I'm also conscious that my history of python environment and package installs - I'm not using virtual envs, they include jupyter and are not Anaconda - could be a source of conflict? Is that even possible?
The initial error I was getting was in the Package Manager in Pro. I got the red exclamation icon that said something like "attempt failed". I didn't screenshot it, unfortunately. And there was no error message or ID assigned the error, so I can't explain why it failed.
I think if you hover your mouse over the red exclamation icon a context window appears after a pause with the same log file readout of the clone process that you would see in the command prompt if you had cloned that way.
I had a look at my history file and it appears to be a summary of conda commands - and for clone commands - the packages installed. However it doesn't have the Traceback when it fails, as per the file I attached earlier in the thread. Is there a way to get this information? Is it stored somewhere else?
i just bought an arduino pro micro clone from amazon it turns out it was from a website called diymore.cc
this is my first arduino so i didnt really know how to set it up but i though it was ready to go out of the box because its an ATMEGA32U4 but i dug around for some drivers and found sparkfun drivers i downloaded and installed them and then the arduino came up on the device manager but i noticed now that it was mis-identifing
We've run into an issue when attempting to create a git-builder for our R packages on our private repository. We are able to clone the repo with a "git clone" command and the relevant credentials, but when we attempt to create a git-builder for this same URL and the same credentials, it returns the following error:
We have imported the HTTPS credentials and verified that those credentials work when doing a simple git clone. We are running behind a proxy, but as I said, we can clone the git repo in question and the package manager is synced to other repositories such as CRAN. We've verified that the PAT is full-scope and we've tried setting AllowUnsandboxedGitBuilds = true per another thread for a similar issue.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
If you have a query related to it or one of the replies, start a new topic and refer back with a link.
LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
Esri has good documentation on installing Python packages via ArcGIS Pro's Package Manager, however, I have had a few clients ask me similar questions over the past couple of years about managing Python packages with ArcGIS Pro, so I have written this LinkedIn article in case it helps anyone.
When you install ArcGIS Pro, the installation will create a default Python Conda environment, which is typically located here: C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3. You should not modify this environment and you should clone the environment as shown in Esri's documentation: -app/latest/arcpy/get-started/clone-an-environment.htm.
Most users are okay with cloning the environment. The issues start when they try to add new Python packages, or when they upgrade ArcGIS Pro and realise their cloned environment has either gone missing, or no longer works.
You can add new packages via ArcGIS Pro's Package Manager, however, sometimes this takes too long to run, and if something goes wrong, it can be difficult to find the cause, and sometimes the package you want may not be available through the Package Manager.
So Esri provide alternative options for installing packages - see the first link above. You can open the Python Command Prompt for the ArcGIS folder in your Windows Start menu, or just navigate to your cloned Conda environment, then use pip, e.g.
Note that when cloning ArcGIS Pro's default Conda environment, there are multiple locations where you can put it. I prefer putting it in the same location as the default Conda environment, i.e. C:\Program Files\ArcGIS\Pro\bin\Python\envs. The reason I do this, is it is easy to find, and also when ArcGIS Pro is upgraded, the clone is automatically removed. Some users may not want this behaviour. They may prefer to have the clone in their Windows user directory, which is fine as long as they remember to upgrade the packages in the clone after they upgrade ArcGIS Pro. I prefer to recreate the clone every time I upgrade ArcGIS Pro. Also, note that when I create a clone, I keep ArcGIS Pro using the default Conda environment, and I only use the cloned environment for running my Python scripts that require ArcPy (unless I am running a custom geoprocessing tool in ArcGIS Pro that needs to use a Python package that is not in the list of default packages).
One of the main issues I see when clients upgrade ArcGIS Pro is they need to recreate their cloned Conda environment, but they are not sure which packages need to be added. They generally find out the hard way when things stop working. For most Python developers, this is not an issue because we can quickly see and fix any issues. However, for large organisations who have scheduled Python tasks running, this can be a big issue and can stop critical systems from working. So, I have written a script below for identifying these packages that need to be added to the new cloned Conda environment.
Before upgrading ArcGIS Pro, you can run this script that will compare your default ArcGIS Pro Conda environment with your cloned Conda environment, and it will tell you which packages are in your cloned environment that are not in the default environment, i.e. the packages that you have installed. Here's the code:
Hi - I'm evaluating Bulk Clone Professional, and need to clone our "template" Epic. This Epic contains a handful of Tasks ("Issues in Epic"). Each of these Tasks in the Epic have a bunch of Sub-Tasks. How do I clone this entire structure? When I clone this "template" Epic using Bulk Clone Professional, I only specify this single Epic as needing to be cloned, because I want to end up with a cloned Epic that contains the same (cloned) Tasks as the source Epic contains, and have each of these (cloned) Tasks point to (cloned) Sub-Tasks.
So in the pic attached, the 5 "Issues in Epic" would also be cloned, and listed in the cloned Epic's "Issues in Epic" section. Also, I need each of the Sub-Tasks (of each Task) to also be cloned. So a full Epic clone.
Hi Kristina - this is Fred, posting by mistake from my manager's account (oops ;_0 ) ... so I go to my project, and click on "view all issues and filters" in the upper right. Make sure the "Advanced" link is clicked, and create a filter that selects the epic you want to clone - along with all of the tasks in that epic. So for me, it's:
Then I save that filter. When you're ready to clone that epic (with its tasks and task sub-tasks), run that filter (by going to your project, clicking on "view all issues and filters", and clicking on the filter you just saved).
795a8134c1