I am using API Axle for my node API.In that i am following this tutorial http://www.cubrid.org/blog/cubrid-appstools/apiaxle-open-source-api-management-analytics-proxy/.In that after i want to see how many hits for a particular API or particular keys..
For that i am using the following link:
http://127.0.0.1:3000/v1/apis/charts
http://127.0.0.1:3000/v1/keys/charts
But its returning results:{}.PLease help me to solve this.Thanks in advance.
Phil from ApiAxle helped me figure this out. It turns out you need to run apiaxle-proxy with the -q flag, or use their separate queue processor. There is some documentation about this here: https://github.com/apiaxle/apiaxle/blob/4b1a80ef576b3af9511c1239e99841b2d521eb63/proxy/apiaxle-proxy.coffee#L533-538
Related
I have a Microsoft Access database, which mdb-ver says is version 'JET4'.
Using the mdb-sql tool, I can query the database. But executing the same SQL query using the node-adodb package returns no data.
Any thoughts on this issue would be much appreciated. Thank you!
[EDIT] -- Thanks for the responses. Sorry for the omission. But the query is really very basic:
SELECT id, dob FROM patients WHERE FirstName='x' AND LastName='y'
My bad! Completely!
The [npm package page][1] showed a number of examples, and I glanced over them without understanding that the "query" method had to be explicitly used to get any results back. I used "execute" instead.
So I'm learning a little bit about Taurus and was trying to apply some pass fail criteria to my .jmx script. When I try to evaluate a specific sampler, it seems to not run the pass fail criteria at all, but if I were to do a simple avg-rt > 10s, continue as failed , this works, but the issue is I want to evaluate each sampler specifically.
Here is a screenshot of my .yml file
I was using this link as reference to follow but I can't seem to get it to work with my script.
https://dzone.com/articles/running-your-load-tests-with-pass-fail-criteria-a
Any help and advice would be appreciated :)
Thank you!
For me it seems to run pass/fail criteria
As you like screenshots here is the screenshot of Taurus YAML file:
And here is the screenshot of "test.jmx" which basically uses simple single Dummy Sampler:
Just in case here is the link to the official documentation of the subsystem: Pass/Fail Criteria
So the issue was that spaces matter lol.
rewriting it as avg-rt of first_navigate>1s, continue as failed does the trick :)
I have this error in the console, below which gives the number 8301. What does this number mean and how can I use it to troubleshoot the error?
(node:8301) DeprecationWarning: current URL string parser is
deprecated, and will be removed in a future version. To use the new
parser, pass option { useNewUrlParser: true } to MongoClient.connect.
Pleas note, I am using this as an example error to try and understand the printed number (node:8301). I don't need help with the error itself.
Please help me to understand node errors.
The number portion of (node:8301) is the node process's process id (pid). This is attached to all warnings that Node.js itself emits, or that are emitted via its process.emitWarning() utility.
(In the particular example in the question, the warning is from a user module using process.emitWarning().)
For what it's worth, NODE_DEBUG also logs pids in the logged information, although strangely not in that format.
I'm not sure if there is actually official documentation on this. There is presently a discussion to add a "Warnings" section to the official documentation: https://github.com/nodejs/node/issues/24987
This question was also asked to https://github.com/nodejs/node/issues/25120, where I discovered and originally answered it.
try this:
MongoClient.connect("mongodb://localhost:27017/YourDB", { useNewUrlParser: true })
from here
Honestly, I’ve been working in node since 2009, and I’ve never bothered to look into the error codes unless I need my software to handle the error. Mostly, I just read the error text.
In the case of your example, the error text clearly tells me what the problem is.
I’ve found generally that the quality of error messages and codes alike varies greatly on the library you’re using.
I have added a custom json ( say for ex: students details instead of cars) inside fabcar.js but when i ran ./startFabric.sh node i still able to see the old data gets loaded into the channel .
Any suggestions would be a great help.
Thanks in advance
I have just restarted the channel and it got worked me !. kudos
I am trying to run a jelly script in JIRA to set the resolution to null for all my issues. The following script runs without errors and returns this:
<JiraJelly xmlns:jira='jelly:com.atlassian.jira.jelly.JiraTagLib' xmlns:log='jelly:log' xmlns:core='jelly:core' xmlns:jx='jelly:xml' xmlns:util='jelly:util'>org.ofbiz.core.entity.GenericValue.NULL_VALUEorg.ofbiz.core.entity.GenericValue.NULL_VALUEorg.ofbiz.core.entity.GenericValue.NULL_VALUE.... </JiraJelly>
Here is the script.
<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraTagLib" xmlns:util="jelly:util" xmlns:core="jelly:core" xmlns:jx="jelly:xml" xmlns:log="jelly:log">
<jira:RunSearchRequest var="issues" />
<core:forEach var="genericIssue" items="${issues}">
<core:invokeStatic className="com.atlassian.jira.issue.IssueImpl" method="getIssueObject" var="issue">
<core:arg type="org.ofbiz.core.entity.GenericValue" value="${genericIssue}"/>
</core:invokeStatic>
<core:invoke on="${issue}" method="setResolution">
<core:arg type="org.ofbiz.core.entity.GenericValue">org.ofbiz.core.entity.GenericValue.NULL_VALUE</core:arg>
</core:invoke>
</core:forEach>
</JiraJelly>
Does any one have any idea why this isn't working or have any ideas on how I might set the resolution to nothing?
Thank you!!
Updating issues via jelly in JIRA is a bit broken. The best example of how to make it work that I've seen is by using ActionDispatcher as shown on the docs page in a comment by Alastair King.
I know it can be done with Jelly runner, but i thinks that this would be easier to do so using the Jira remote API or the Jira CLI. A more elaborated example of the Jira remote API can be found here. If anyone wants me to post a working source code feel free to ask.