After updating Anylogic to PLE 8.8.0 (macOS 10.13.6), "Choose Probability Distribution..." wizard is not showing any description of distributions and labels of arguments are just labeled as "arg0", "arg1", "arg2"...
Is anyone else experiencing the same?
Tnx!
correct.. this seems to be a bug, not only with distributions but many functions now have arg instead of the name of the variable that is indicative of its meaning
Related
I would like to know if there is a way to run certain step in Octopus from one version onward.
I see this may be achieved by defining different channels and some "Version Rules", but I think there must be a way to do this by a "Run Condition" on the step.
I saw here that you can compare versions on Octopus.
I would like to define something like this in my "Run Condition":
#{if Octopus.Release.Number > 2.3.15}True{/if}
But I don't know exactly how to write this condition. Please let me know if you can help me.
This is necessary because sometimes we add new packages (+ step) to an existing deployment, but deployments for old releases are still being creating.
Thanks in advance.
Based on benPearce answer I solved my situation like this:
In a powershell step called "Check Version" I wrote:
$IsOver2315 = $OctopusParameters["Octopus.Release.Number"] -gt [version]"2.3.15"
Set-OctopusVariable -name "IsOver2315" -value (&{If($IsOver2315) {"True"} Else {"False"}})
And in the "Run Condition" I wrote:
#{Octopus.Action[Check version].Output.IsOver2315}
Thanks benPearce
The Octostache expressions don't allow logic like this, but you can put that calculation into a script step which outputs a boolean variable that Octostache can evaluat.e
In Xcode, under Preferences (command+comma), in the Behaviors section, there is an option to "Speak announcement using". This option has a pull down list of women's names. I have tried several women's names, and they all seem to be speaking a (different?) foreign language.
Which woman's name corresponds to English? Or better yet, what is the corresponding language for each name? There are a lot of names for me to sift through.
I'm on macOS Sierra if it makes a difference.
Following up here to save people some time, the en_US voices from say -v ? are:
masculine: Alex, Fred
feminine: Samantha, Victoria
Fred and Victoria have very robotic voices so I would recommend choosing either Alex or Samantha.
You can type: say -v ? in terminal to see the list ov all voices and their languages
Like you've said: Samantha is reading using en_US.
Oh Good Grief! I stumbled upon the right name while writing this question: Samantha.
The reasons I wrote this question was because I was tired of trying out different names looking for English, and I was not being disciplined in changing the name after each build, and I was forgetting my place from my progress yesterday.
In the composing of this question, I chose my next name to test: "Samantha" and sure enough on my next build I heard English. I guess I gave up too early, but it was looking hopeless for a while.
Still, it would be nice if there was a list of corresponding languages to names.
As denoted in This Article ReSharper's .sln.DotSettings file contains only those settings which values changed from default ones. Is there a way to store all the code editting and code inspection settings in a team-shared layer, regardless of the value being changed or default?
The only way to do this I see is changing each and every value and switching it back (so all of them end up in .sln.DotSettings file), however this seems to be quite a time-consuming task.
The problem I'm trying to avoid is as follows:
Suppose a team has 2 developers, say Jessika and John, and they decide that they are OK with Resharper's default to prefix private fields with with an underscore:
int _myPrivateField = 1;
So they are not changing the "Instance fields(private)" setting under "C# Naming Style" section and check in the .sln.DotSettings file.
However, when Jessica checks out the source code on her home laptop it Resharper still suggests using
int myPrivateField = 1;
because her computer has its setting changed to have no prefix, saved as "Save to this computer". As denoted in Resharper's docs if a "This Computer" layer has a value for a setting, whereas the other layers don't the value will be applied (see the middle green setting in this picture: http://blogs.jetbrains.com/dotnet/wp-content/uploads/2012/08/layers3.png
Regrettably, at the moment we can offer no option other than changing options one by one and saving them in the requisite layers. We are aware that this approach is inconvenient, and are in discussions as to how to best handle this.
I can only select Active and Closed as state and Issue Resolved as reason when editing a workitem in VS2010. I have consulted the TFS Power Tools work item field explorer and it shows me a bunch of possible values for System.Reason and System.State.
Does the process template affect the options (I'm using the default MSF agile template), am I blind or is something wrong here?
Best reagards
It sounds like you have a work item of type "Issue". The process template defines both work item types, possible states for each work item type as well as state change transition rules. While there are many possible values for System.Reason and System.State, the "issue" work item type is very limited.
The "issue" type can only be in states "active" or "closed". When moving from "active" to "closed", the only possible reason is "issue resolved". When moving back from "closed" to "active", the only possible reason is "reactivated."
More information about the "issue" work item type is available on MSDN.
As you note, the "issue" work item type is fraught with limitations. It's often more useful to use a bug or a task work item type to define work that needs to be done in your sprint.
In the agile for msf template which you are using, the default workflow for issues is as you mentioned: from active to closed.
If you wish to change it, you may modify the issue's work item type definition. You may use the tfs power tools to do so with a graphic interface, or edit the xml and upload it with the command line.
Other templates and other work item types have different workflows.
Select a method
Selection http://synapticmishap.co.uk/aSO/SelectionGrab.jpg
Edit > Refactor...
Select "Move Up"
I get the following error a lot.
Refactoring Error http://synapticmishap.co.uk/aSO/RefactoringError.jpg
Any ideas on how I can get Xcode to, well, do its job?
Solution Summary
Option 2 that Peter suggests below did the trick. I can't believe that
a) I didn't try this Smacks head
and
b)
Xcode couldn't find a sane way of saying "Don't select the whole method!"
Two possibilities:
Maybe that blank line at the start is screwing it up? Try starting the selection at the -/+.
Try right-clicking the first segment of the selector and Refactoring that.
I tried refactoring a class (implementation) after I renamed the containing file manually and got the same error. Once I renamed the file back to its original name I was able to refactor.