Powershell – Get-Job by State and Name

powershellpowershell-3.0

Powershell v3.

Start-Job -Name "TestJob" -ScriptBlock { Write-Host "foo" }

The job starts fine. I then type

Get-Job

and I see

Id   Name      PSJobTypeName   State      HasMoreData   Location      Command
--   ----      -------------   -----      -----------   --------      -------
18   TestJob   BackgroundJob   Completed  True          localhost     Write-Host "foo"

Everything is going according to plan so far. But now let's say I have many jobs running in this session, and they have various different names. So I want to find only the jobs that are named TestJob:

Get-Job -Name TestJob

This also works exactly as expected, returning only the jobs of that name. But now let's say I want to find jobs that both have the name TestJob and are still running:

PS C:\> Get-Job -Name TestJob -State Running
Get-Job : Parameter set cannot be resolved using the specified named parameters.
At line:1 char:1
+ Get-Job -Name TestJob -State Running
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Get-Job], ParameterBindingException
    + FullyQualifiedErrorId : AmbiguousParameterSet,Microsoft.PowerShell.Commands.GetJobCommand

Is there a way to do this?

Best Answer

Try the following

Get-Job -State Completed | Where-Object {$_.Name.Contains("TestJob")}

Here's a sample run based on your example

PS D:\>  Get-Job -State Completed | Where-Object {$_.Name.Contains("Job")}

Id              Name            State      HasMoreData     Location             Command
--              ----            -----      -----------     --------             -------
1               TestJob         Completed  True            localhost             Write-Host "foo"
3               TestJob         Completed  True            localhost             Write-Host "foo"

See Get-Help Where-Object for more info on this.

Related Solutions

Powershell – Passing Powershell variables into a scriptblock

You can pass values via the -arguments parameter and refer to them as $args[0] and so on inside the script block:

Invoke-Command -Session $s -Scriptblock {
    cd "C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server Resource Kit\BlackBerry Enterprise Server User Administration Tool Client"
    ./BESUserAdminClient -username $args[0] -password $args[1] -ad_auth -domain staging -b bbbes -u $args[2] -change -wrandom
} -argumentlist $username $password $u

Or define the parameters inside the script block and use named parameters:

Invoke-Command -Session $s -Scriptblock {
    param(
        $username,$password,$u
    )

    cd "C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server Resource Kit\BlackBerry Enterprise Server User Administration Tool Client"
    ./BESUserAdminClient -username $username -password $password  -ad_auth -domain staging -b bbbes -u $u -change -wrandom
} -argumentlist $username $password $u

Python – How to handle “413: Request Entity Too Large” in python flask server

Flask is closing the connection, you can set an error handler for the 413 error:

@app.errorhandler(413)
def request_entity_too_large(error):
    return 'File Too Large', 413

Now the client should get a 413 error, note that I didn't test this code.

Update:

I tried recreating the 413 error, and I didn't get a ConnectionError exception.

Here's a quick example:

from flask import Flask, request

app = Flask(__name__)

app.config['MAX_CONTENT_LENGTH'] = 1024


@app.route('/post', methods=('POST',))
def view_post():
    return request.data


app.run(debug=True)

After running the file, I used the terminal to test requests and sending large data:

>>> import requests
>>> r = requests.post('http://127.0.0.1:5000/post', data={'foo': 'a'})
>>> r
<Response [200]>
>>> r = requests.post('http://127.0.0.1:5000/post', data={'foo': 'a'*10000})
>>> r
<Response [413]>
>>> r.status_code
413
>>> r.content
'<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">\n<title>413 Request Entity Too Large</title
>\n<h1>Request Entity Too Large</h1>\n<p>The data value transmitted exceeds the capacity limit.</p>\n'

As you can see, we got a response from flask 413 error and requests didn't raise an exception.

By the way I'm using:

Flask: 0.10.1
Requests: 2.0.0

Best Answer

Related Solutions

Powershell – Passing Powershell variables into a scriptblock

Python – How to handle “413: Request Entity Too Large” in python flask server

Related Topic