This question already has answers here:
Error: Protocol not available, dumping backtrace [duplicate]
(4 answers)
Closed 9 months ago.
As of beta2, I'm getting this message every two seconds after I create an audio output unit:
2016-10-14 11:31:21.572479 MyProduct[94063:8294923] [aqme] 254: AQDefaultDevice (173): skipping input stream 0 0 0x0
Anyone know what it's generated by?
I'd thought that perhaps I wasn't servicing an audio out callback, but as far as I can tell, I'm servicing it properly.
A cleaner solution (than the one given by user6026720) that fixes Simulator logs without affecting Device logs is available at https://stackoverflow.com/a/39651073/1033581:
Under Product > Scheme > Edit Scheme... > Run, set the OS_ACTIVITY_MODE environment variable to ${DEBUG_ACTIVITY_MODE} so it looks like this:
Go to your project build settings, and click + to add a User-Defined Setting named DEBUG_ACTIVITY_MODE. Expand this setting and Click the + next to Debug to add a platform-specific value. Select the dropdown and change it to "Any iOS Simulator SDK". Then set its value to "disable" so it looks like this:
Related
I am connected to our target over ethernet using the Linux TCF agent to debug an application.
I've used a lot of debuggers over my 25 year career, but this is my first time using Eclipse/Linux/Xilinx environment. I can set break points. I can single step through the code. I can view variables. I can view memory. I can type a new value in the memory location, but the variable value doesn't change. I tried to click or double click the value in the Variables pane. I tried right clicking to see if it would give me an option to modify the value.
I'm not sure what good a debugging tool is if I can't change a variable value to alter the execution path of my software...
In addition to the hacky solution we came up in the comments, which is to get the address of a variable and then modify them through the mr command from the xsct console, the same console provide commands to properly get/set a local variable.
The syntax is the following:
locals [options] [variable-name [variable-value]]
And an example:
locals my_int_var 10
locals my_float_var 1.4
This question already has an answer here:
JMeter - submit JMeter function inside a script (JSR223 element)
(1 answer)
Closed 1 year ago.
I use groovy to write a script. In the screenshot, No. 1 works, No. 2 doesn't work, No. 3 works. It's normal to print No. 1 separately. No. 2 and No. 3 are written in a custom function. The parameter passed in by No. 2 is still ${re} instead of value
Don't inline JMeter Functions or Variables into Groovy scripts, your "No 1" and "No 3" work because they're GStrings and your "No 2" conflicts with JMeter Functions and/or Variables syntax.
So I would recommend moving your function into "Parameters" tab like:
Also according to JSR223 Sampler documentation:
Or Use Script Text and check Cache compiled script if available property.
When using this feature, ensure your script code does not use JMeter variables or JMeter function calls directly in script code as caching would only cache first replacement. Instead use script parameters.
So if your ${secretKey} variable changes from iteration to iteration only first value will be used and this may ruin your test so you might want to change it to vars.get('secretKey') expression
Also be aware that according to 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure article you should always be using the latest version of JMeter so consider upgrading to JMeter 5.4.1 (or whatever is the latest stable version available at JMeter Downloads page) on next available opportunity.
I'm trying to implement some simple text editing functionality in a TUI I'm working on. I'm using the Python wrapper for curses.
Currently what I'm trying to do is associate certain key-binds to a particular function or operation, but unsure of how to do it and the documentation isn't clear. According to the documentation there are some default keybinds, but what if I wanted to add my own "event" associated with a particular keybind?
The place to start is by looking at the source code of curses.textpad to see how it is implemented. It's hardcoded, e.g.,
elif ch == curses.ascii.ENQ: # ^e
if self.stripspaces:
self.win.move(y, self._end_of_line(y))
else:
self.win.move(y, self.maxx)
It could be rewritten to allow for custom bindings, but keep in mind that at the moment (mid-February 2021), the most recent commit was more than 4 years ago (December 2016).
so I have my computer set up as an agent pool in azure-devops. I'm creating a test for latency so the developers can use it in their CI, the script runs in python and test various points in a system I have set up for the company which is connected to the cloud, it's mainly for informative purposes. When I run the script I have to wait some time, so the system I have connected goes through its normal network cycle inspecting all the devices in the local network, not very important for que question, however when I'm waiting I show in the terminal a message with "..." going from "." to ".." to "...", just to show the script didn't crash or anything.
the python code looks like this and works just fine when I run it locally:
sys.stdout.write("\rprocessing queue, timing varies depending on priority" + ("."*( i % 3 + 1))+ "\r")
sys.stdout.flush()
however the output shown in the azure pipeline shows all of the lines without replacing them. Is there a way to do what I want?
I am afraid showing progress is not supported in azure pipeline. Azure pipeline log console isnot user interactive. It just capture the agent machine terminal outputs.
You might have to use a simpler way to indicate that the script is now executing and not finished yet. For simple example:
sys.stdout.write("Waiting for processing queue ..." )
You can report this problem to microsoft development team. Hope they find a way to fix this in the future sprint.
I have seen it once but never actually used it myself, this can be done in both bash and PowerShell, not sure if this works inside a Python script, you might have to call bash/PowerShell from within your Python script.
It is possible to set a progress value in percent that is visible outside of the log, but as I understand it this value is step-spefific, meaning it only applies to the pipeline step you're currently in. You could drag the numeric value (however many percent) along into the next step, but the progress counter would then again show up in the next step. I believe it is not possible to have a pipeline global display of a progress.
If you export a progress value it will show up beside the step name in the left hand side step list.
This setting of a progress (also exporting one variable from one step to another, which is typically done that way) can be done by echoing special logging commands. There's a great description to be found here: Logging commands
What you want to do is something just as it is shown as an example on the linked page:
echo "Begin a lengthy process..."
for i in {0..100..10}
do
sleep 1
echo "##vso[task.setprogress value=$i;]Sample Progress Indicator"
done
echo "Lengthy process is complete."
All of these special logging commands start with ##vso[task... The VSO is a relict to the time when Azure DevOps was called Visual Studio Online.
There are a whole bunch of them, but most of the time what you really need is exporting variables from one build step context to another, which is done with ##vso[task.setvariable]value
This question already has answers here:
What happened to regtlibv12?
(3 answers)
Closed 3 years ago.
I have Visual Studio 2015 running on Windows 10 and need to register a legacy type lib (.tlb). From the posts I've found, regtlibv12.exe is the tool for this. However, I can't find it under C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ or anywhere else for that matter. Does anyone know how to register .tlb if regtlibv12.exe doesn't exist?
I've tried regasm /tlb:path but I get errors saying the path cannot be read.
Any help would be much appreciated.
You need to get the old regtlibv12.exe from an older machine.
I upgraded to Windows 10 and lost the function but found it here:
C:\Windows.old\Windows\Microsoft.NET\Framework\v4.0.30319
works fine.