parameter-passing

Here is a sample JSON response from my curl: { "success": true, "message": "jobStatus", "jobStatus": [ { "ID": 9, "status": "Successful" }, { "ID": 2, "status": "Successful" }, { "ID": 99, "status": "Failed" } ] } I want to check the status of ID=2. Here is the command I tried: cat test.txt|jq --arg v "2" '.jobStatus[]|select(.ID == $v)|.status' response: there is none I tried value 2 without quotes and still no result. By contrast, if I try the command with a literal 2 , it works: cat test.txt | jq '.jobStatus[]|select(.ID == 2)|.status' response: "Successful" I'm stuck. Can anyone help me

For SqlDataSource I can configure the external source for the incoming paramater. For example it might be a QueryString, Session, Profile and so on. However I do not have an option to use User as a source. I know that I could provide value for the parameter in Inserting,Selecting,Updating,Deleting events. But I do not think that this is an ellegant solution because I have some parameteres already definied in aspx file. I do not want to have parameters defined in two separate places. It makes mess. So can I somehow define this parameter in .aspx file? <SelectParameters> <asp

I'm having an issue passing variables to a Bash script using QSub. Assume I have a Bash script named example. The format of example is the following: #!/bin/bash # (assume other variables have been set) echo $1 $2 $3 $4 So, executing "bash example.sh this is a test" on Terminal (I am using Ubuntu 12.04.3 LTS, if that helps) produces the output "this is a test". However, when I enter "qsub -v this,is,a,test example.sh", I get no output. I checked the output file that QSub produces, but the line "this is a test" is nowhere to be found. Any help would be appreciated. Thank you. Using PBSPro or

What is better to do? self.call(1, True, "hi") or self.call(1, True, "hi",) And what in the following cases: self.call( 1, True, "hi" ) or self.call( 1, True, "hi", ) ? Reasons for adding a trailing comma in data structures are familiar to me, but what about function calls? Jacob Wan I think there's no technical reason to avoid trailing commas in function calls, but some people probably do find them distracting. Some may stop and say: "Hmmm, I wonder if that's really supposed to be there?" I hesitate to call this a benefit, but one effect of using trailing commas in conjunction with an

If I call a matlab function with: func(1,2,3,4,5) it works perfectly. But if I do: a=[1,2,3,4,5] %(a[1;2;3;4;5] gives same result) then: func(a) gives me: ??? Error ==> func at 11 Not enough input arguments. Line 11 in func.m is: error(nargchk(5, 6, nargin)); I notice that this works perfectly: func(a(1),a(2),a(3),a(4),a(5)) How can I use the vector 'a' as a parameter to a function? I have another function otherfunc(b) which returns a, and would like to use its output as a paramater like this func(otherfunc(b)) . Comma-seperated lists (CSL) can be passed to functions as parameter list, so what