Push and update plugin - bazaar

1.I was trying to use the push-and-update plugin and failed. after solving the reported error (i change the plugin folder name to push_and_update) all errors disappeared , but its seems that nothing happened --> the "remote" branch still needs to be updated manually.
Please help.
I tried to attach an detailed description of an workflow i prepared , in order to get your comments. the upload was failed due to the fact that i'm new user in this forum. do i have another way to attach image?
thanks
Gil Idelson

I think there must already exist a workingtree on the server.
You can use bzr checkout to create one.

Related

ADF Azure data Factory debug not running saved changes

Anyone see this behavior? For example here is my code in an activity....#{concat(
substring(activity('GetMaxDate').output.firstRow.MAX_DATE,0,4)
This IS saved. Multiple times. But when I run in debug this is what is run...
#{concat(\n substring(activity('GetMaxDate').output.firstRow.MAX_DATE,1,4)\n ,'
It's running the prior version (0,4) instead of the new version (1,4). I first noticed this because I changed the name of the activity and debug still ran the old name. This seems like new problem I've not had before. If I publish and run it as trigger it picks up the change. It's just debug that's not picking it up. This seems an inexcusable bug. This is 101 functionality folks.
Any suggestions? Should this be logged with Microsoft as bug?
Additinal option to Gary's comment:
C) Rename your pipeline, save, run debug. Rename back after.
This worked for me.
Seen this cache behavior in the past. Preview query shows cached data from source table even though the source table data was completely changed.
Deleting the pipeline,dataset.. and creating new pipeline solved the issue for me.
Seems this happenens when the debug is being used too many times. Recommend to log this behavior as a bug.

"Your lab is in a failed state"

I have twice experienced that a lab ends up in a failed state. All I can do is remove and re-create the lab.
Is there anyway one can prevent this from happening? Or at least be able to recover the lab master VM?
Thank you for reporting the issue! We're investigating the root cause right now. We'll keep you updated on the status here. Currently we have not yet identified a workaround.
This issue has been resolved! Please try again.
We reached out to the Product Team and it appears this was a known issue which is now resolved.
Please try to create the lab again.
Here is a blog post update for this.

Dynamics CRM Unable to Uninstall Managed Solution

I've currently got an issue in our Dynamics CRM test environment, we currently cannot 'uninstall' the managed solution we have imported from our development environment.
The error we are getting when we try to uninstall is: "[entity] doesn't have a valid quick find query defined for it.". The log that they allow you to download with 'more details' essentially says the same thing with an error code of -2147089917.
I can't find any information on google or in the dynamics documentation around what could cause this issue or what it means.
We have done some basic customisation to the quick find query for that entity which appears to be in the solution. We can use the search and it uses the quick find query we have defined so that appears to be correct.
The solution we have is exported from our development environment and then imported as a managed solution to the test environment.
We've tried importing a newer version of the same solution over the top and we still can't delete.
Does anyone have any ideas as to what could cause/solve this issue.
Thanks,
Michael
you have to remove the entities existing in the solution which you want to uninstall from the Quick find Search before deleting the solution.
To do this:
go to Settings > Administration > System Settings
In the tab marked “General” you will see a heading called “Set up Quick Find”
Select the record entities that you would like to remove and click OK
And now you should be able to uninstall your solution.
Hope this help!
Thinks,
Youssef.

Unable to create account for installing Oracle Database

So I was looking for installing an Oracle 12c database on my Windows 8 laptop, so that I could learn much of SQL(after posting my last question).
I have downloaded all the needed zips. obviously while trying I got error:
[INS-30131] Initial setup required for the execution of installer validations failed.
Additional Information:
- Framework setup check failed on all the nodes
- Cause: Cause Of Problem Not Available
- Action: User Action Not Available
Summary of the failed nodes
hp
- Version of exectask could not be retrieved from any node
- Cause: Cause Of Problem Not Available
- Action: User Action Not Available
Well after looking into many posts on SO, I figured out that it needs some hidden User account (C$). I got steps for setting up such a account but unfortunately they are not working for me.
Following the path as: Control Panel>Administrative Tools> Computer Management>Shared.
As mentioned in steps across internet, there is no option for me to create a new account.
Apart from that, I have tried changing my Username and also I have tried using default Administrator account but nothing seems working.
I am pretty sure this is not new so somebody out there must have a solution to this issue. Pls advice...
This is the description of the error, I saw it, but was trying to find an idea how to fix it.
Anyway, I solved it by renaming the volume group and updating accordingly the fstab and the grub.conf.

How to troubleshoot TFS error TF237086 "The work item cannot be saved..."

I am getting the following error in a TFS 2010 build:
The work item '59' could not be updated: 'TF237086: The work item cannot be saved because at least one field contains a value that is not allowed.'
Work item 59 is a basic task I created to associate with my changeset on check-in. I have done no customization to the "task" work item. I get no errors when opening the task up and changing values manually. There is nothing in the build log that gives any clues as to what field is causing the problem.
How can I troubleshoot this issue?
Something I would do in this case:
Check the build service account, there's a high chance that when the work item is associated, its ChangedBy field is updated with this account and the value is not valid. Somebody in MSDN forum suggested checking the list of valid TFS users for a work item (you can open a bug and try typing the name in the AssignedTo field) and see if this account is in that list.
Try a checkin by yourself with the same associated task and see what fields are updated (you should be able to see this in the History tab), from there you can figure out the possible fields, and hopefully can guess the one that is in trouble.
If none of this works, I can get some more details and try to repro it on my machine. We'll need to improve error message to specify which fields that are invalid.
Hope this helps.
[Update]
The cause was indeed that the build service account (NT AUTHORITY\SYSTEM) did not have permissions to modify work items. All my attempts to fix this by editing group memberships failed, but I did get the build working without errors by using an unused project contributor's account as the build service account. Changing build service account may require the old build workspaces to be renamed or reassigned.
I had the same issue, after restarting VS 2015 IDE and entering credentials to my account on the TFS I was able to get rid of the errror.
After changing the build service account, I got a new error
The working folder xxxx is already in use by the workspace
1_1_SSSSSSSS;NT AUTHORITY\SYSTEM on computer SSSSSSSSS.
The solution to that issue is to use the TF utility to delete the workspace(s) associated with the SYSTEM build account. I had to copy the TF utility from my Laptop over to our server to run it.
See TFS Build Service Account change causes Build Failures - “Working Folder in use” Failures
Got the error on a long running build system where the user accounts had not changed.
found the WORKSPACE ID in the build log ran
tf.exe workspaces /owner:*
to confirm the workspace was on the build server and then ran
tf.exe workspace /delete 9_1_BUILDSERVER;OURDOMAIN\TFSBuild
to delete it, queued another build and no further problem.
If you changed process type, can throw this exception. Please correct your process type. My problem solved with the action.