Python worker fails to start with "The operation has timed out"

The python process sometimes fails to start up with an operation time out. In one case, an execution started because of "RunOnStartup", and the solution was for the process to start again. In a second case (reported below), we see that the process keeps failing to start with the same pattern:
[1/14/20 3:58:29 PM] Starting worker process failed
[1/14/20 3:58:29 PM] The operation has timed out.

Per @6403wency413:
Issue with ServiceBusTrigger with an output below.

[1/14/20 3:56:34 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=3a8610b8-cfdd-4151-9a6c-ab2e649bc111)
[1/14/20 3:56:34 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 1, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:01:27 PM, SessionId: (null)
[1/14/20 3:57:29 PM] Starting worker process failed
[1/14/20 3:57:29 PM] The operation has timed out.
[1/14/20 3:57:29 PM] Starting worker process:python  /Users//.vscode/extensions/ms-python.python-2020.1.57204/pythonFiles/ptvsd_launcher.py --default --host <IP_ADDRESS> --port 9091 --wait "/usr/local/Cellar/azure-functions-core-tools/2.7.1948/workers/python/3.7/OSX/X64/worker.py" --host <IP_ADDRESS> --port 65522 --workerId f03ddfda-8755-47ef-bea4-5f773263a205 --requestId c31e8c64-6fda-4f9d-bc4d-a7eb4312f39b --grpcMaxMessageLength 134217728
[1/14/20 3:57:29 PM] python process with Id=18081 started
[1/14/20 3:57:29 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=3a8610b8-cfdd-4151-9a6c-ab2e649bc111)
[1/14/20 3:57:29 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:29 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:29 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:29 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=755bec73-3bc2-417f-90f0-139dfe7fa9a8)
[1/14/20 3:57:29 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 2, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:02:23 PM, SessionId: (null)
[1/14/20 3:57:29 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=755bec73-3bc2-417f-90f0-139dfe7fa9a8)
[1/14/20 3:57:29 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:29 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:29 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:29 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=a22e1407-70f1-4c42-aea1-ceb71c234011)
[1/14/20 3:57:29 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 3, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:02:23 PM, SessionId: (null)
[1/14/20 3:57:29 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=a22e1407-70f1-4c42-aea1-ceb71c234011)
[1/14/20 3:57:29 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:29 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:29 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:29 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=9a2b5e59-0c80-4955-b40f-a0fa6acbada5)
[1/14/20 3:57:29 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 4, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:02:23 PM, SessionId: (null)
[1/14/20 3:57:29 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=9a2b5e59-0c80-4955-b40f-a0fa6acbada5)
[1/14/20 3:57:29 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:29 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:29 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=25f0a5b8-0d3e-4575-8aa5-eacce3f129bf)
[1/14/20 3:57:30 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 5, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:02:23 PM, SessionId: (null)
[1/14/20 3:57:30 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=25f0a5b8-0d3e-4575-8aa5-eacce3f129bf)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=aa16462a-d7fb-4f39-b879-addfab270a39)
[1/14/20 3:57:30 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 6, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:02:23 PM, SessionId: (null)
[1/14/20 3:57:30 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=aa16462a-d7fb-4f39-b879-addfab270a39)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=f5b835e8-737b-4c1d-adab-ea8da75368d6)
[1/14/20 3:57:30 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 7, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:02:23 PM, SessionId: (null)
[1/14/20 3:57:30 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=f5b835e8-737b-4c1d-adab-ea8da75368d6)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=177a95b6-c3fc-4842-83ba-f2f5a707e4dc)
[1/14/20 3:57:30 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 8, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:02:24 PM, SessionId: (null)
[1/14/20 3:57:30 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=177a95b6-c3fc-4842-83ba-f2f5a707e4dc)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=ecbaea2b-8c7e-402f-b569-a50f57759334)
[1/14/20 3:57:30 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 9, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:02:24 PM, SessionId: (null)
[1/14/20 3:57:30 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=ecbaea2b-8c7e-402f-b569-a50f57759334)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Executing 'Functions.azurecleanupimages' (Reason='New ServiceBus message detected on 'iri6-servicebusqtest'.', Id=f37c51cd-07dc-4b60-88b9-24c8cb5bf3c2)
[1/14/20 3:57:30 PM] Trigger Details: MessageId: db791f7052684d7997a75d092f4cf6e1, DeliveryCount: 10, EnqueuedTime: 1/14/20 3:56:25 PM, LockedUntil: 1/14/20 4:02:24 PM, SessionId: (null)
[1/14/20 3:57:30 PM] Executed 'Functions.azurecleanupimages' (Failed, Id=f37c51cd-07dc-4b60-88b9-24c8cb5bf3c2)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:57:30 PM] Message processing error (Action=UserCallback, ClientId=MessageReceiver1iri6-servicebusqtest, EntityPath=iri6-servicebusqtest, Endpoint=iri6-servicebusnstest.servicebus.windows.net)
[1/14/20 3:57:30 PM] System.Private.CoreLib: Exception while executing function: Functions.azurecleanupimages. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[1/14/20 3:58:29 PM] Starting worker process failed
[1/14/20 3:58:29 PM] The operation has timed out.
[1/14/20 3:58:29 PM] Starting worker process:python  /Users/**/.vscode/extensions/ms-python.python-2020.1.57204/pythonFiles/ptvsd_launcher.py --default --host <IP_ADDRESS> --port 9091 --wait "/usr/local/Cellar/azure-functions-core-tools/2.7.1948/workers/python/3.7/OSX/X64/worker.py" --host <IP_ADDRESS> --port 65522 --workerId 176e1989-b35c-4a88-92af-18309646b17f --requestId 46326407-b8a5-4cf1-8620-d7e60964261c --grpcMaxMessageLength 134217728
[1/14/20 3:58:29 PM] python process with Id=18089 started
[1/14/20 3:59:29 PM] Starting worker process failed
[1/14/20 3:59:29 PM] The operation has timed out.
[1/14/20 3:59:29 PM] Exceeded language worker restart retry count for runtime:python. Shutting down Functions Host
[1/14/20 3:59:29 PM] Stopping host...
[1/14/20 3:59:29 PM] Stopping JobHost
[1/14/20 3:59:29 PM] Job host stopped
[1/14/20 3:59:29 PM] Host shutdown completed.
Application is shutting down...

I'm using Azure functions in my dissertation project and have a deadline. Would someone be kind enough to suggest the scope of this issue so I can find a workaround i.e. is it just local python function development in vs code, or all python functions... Also when the next release may be. I would be very grateful for this 😁

@fisherjames have you actually encountered this ? Scope is very few people have encountered it very rarely. So go ahead and use it. :)

@fisherjames have you actually encountered this ? Scope is very few people have encountered it very rarely. So go ahead and use it. :)

I have encountered this, I get the errors "worker failed to start" and "did not find any initialized language workers", running latest VS Code build on a MacBook Pro with latest OS updates.
I'm trying to write a function to query Twitter API using Tweepy and store tweets in Azure blob. If I can't fix this issue then I will have to write a C# function with different Twitter library I suppose.

Got it - are you seeing this consistently/or is it intermittent ? If you have a consistent repro we would like to work with you to see if we can find the root cause.

Got it - are you seeing this consistently/or is it intermittent ? If you have a consistent repro we would like to work with you to see if we can find the root cause.

Consistent. That's would be great, thanks. Once I'm home I will post the conditions/configuration of my setup.

VS Code info
Version: 1.41.1
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T14:57:51.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 18.7.0
extensions.json
{   "recommendations": [     "ms-azuretools.vscode-azurefunctions",     "ms-python.python"   ] }
launch.json
{   "version": "0.2.0",   "configurations": [     {       "name": "Attach to Python Functions",       "type": "python",       "request": "attach",       "port": 9091,       "preLaunchTask": "func: host start"     }   ] }
settings.json
{   "azureFunctions.deploySubpath": ".",   "azureFunctions.scmDoBuildDuringDeployment": true,   "azureFunctions.pythonVenv": ".venv",   "azureFunctions.projectLanguage": "Python",   "azureFunctions.projectRuntime": "~2",   "debug.internalConsoleOptions": "neverOpen",   "python.pythonPath": ".venv/bin/python3", }
tasks.json
{   "version": "2.0.0",   "tasks": [     {       "type": "func",       "command": "host start",       "problemMatcher": "$func-watch",       "isBackground": true,       "dependsOn": "pipInstall"     },     {       "label": "pipInstall",       "type": "shell",       "osx": {         "command": "${config:azureFunctions.pythonVenv}/bin/python -m pip install -r requirements.txt"       },       "windows": {         "command": "${config:azureFunctions.pythonVenv}/Scripts/python -m pip install -r requirements.txt"       },       "linux": {         "command": "${config:azureFunctions.pythonVenv}/bin/python -m pip install -r requirements.txt"       },       "problemMatcher": []     }   ] }
Function code
`import datetime
import logging
import tweepy
import azure.functions as func
consumer_key = 'xxxxxxxxxxxxxxxxxxxxxxxxxx'
consumer_secret = 'xxxxxxxxxxxxxxxxxxxxxxxxxx'
access_token = 'xxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxx'
access_token_secret = 'xxxxxxxxxxxxxxxxxxxxxxxxxx'
def main(mytimer: func.TimerRequest) -> None:
utc_timestamp = datetime.datetime.utcnow().replace(
tzinfo=datetime.timezone.utc).isoformat()
if mytimer.past_due:
    logging.info('The timer is past due!')

logging.info('Python timer trigger function ran at %s', utc_timestamp)

auth = tweepy.OAuthHandler(consumer_key, consumer_secret)
auth.set_access_token(access_token, access_token_secret)

api = tweepy.API(auth)

public_tweets = api.home_timeline()
for tweet in public_tweets:
    print(tweet.text)`

Output showing exceptions
`> Executing task: .venv/bin/python -m pip install -r requirements.txt <
Requirement already satisfied: azure-functions in ./.venv/lib/python3.7/site-packages (from -r requirements.txt (line 1)) (1.0.8)
Requirement already satisfied: tweepy in ./.venv/lib/python3.7/site-packages (from -r requirements.txt (line 2)) (3.8.0)
Requirement already satisfied: six>=1.10.0 in ./.venv/lib/python3.7/site-packages (from tweepy->-r requirements.txt (line 2)) (1.14.0)
Requirement already satisfied: requests-oauthlib>=0.7.0 in ./.venv/lib/python3.7/site-packages (from tweepy->-r requirements.txt (line 2)) (1.3.0)
Requirement already satisfied: PySocks>=1.5.7 in ./.venv/lib/python3.7/site-packages (from tweepy->-r requirements.txt (line 2)) (1.7.1)
Requirement already satisfied: requests>=2.11.1 in ./.venv/lib/python3.7/site-packages (from tweepy->-r requirements.txt (line 2)) (2.22.0)
Requirement already satisfied: oauthlib>=3.0.0 in ./.venv/lib/python3.7/site-packages (from requests-oauthlib>=0.7.0->tweepy->-r requirements.txt (line 2)) (3.1.0)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in ./.venv/lib/python3.7/site-packages (from requests>=2.11.1->tweepy->-r requirements.txt (line 2)) (1.25.8)
Requirement already satisfied: idna<2.9,>=2.5 in ./.venv/lib/python3.7/site-packages (from requests>=2.11.1->tweepy->-r requirements.txt (line 2)) (2.8)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in ./.venv/lib/python3.7/site-packages (from requests>=2.11.1->tweepy->-r requirements.txt (line 2)) (3.0.4)
Requirement already satisfied: certifi>=2017.4.17 in ./.venv/lib/python3.7/site-packages (from requests>=2.11.1->tweepy->-r requirements.txt (line 2)) (2019.11.28)
You are using pip version 19.0.3, however version 20.0.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Terminal will be reused by tasks, press any key to close it.

Executing task: . .venv/bin/activate && func host start <

Found Python version 3.7.4 (python).
              %%%%%%
             %%%%%%
        @   %%%%%%    @
      @@   %%%%%%      @@
   @@@    %%%%%%%%%%%    @@@
 @@      %%%%%%%%%%        @@
   @@         %%%%       @@
     @@      %%%       @@
       @@    %%      @@
            %%
            %

Azure Functions Core Tools (3.0.2106 Commit hash: 5431fca4f603bf9446d7dd2d5f96a43b5f69b5cb)
Function Runtime Version: 3.0.13107
[07/02/2020 19:09:03] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:java
[07/02/2020 19:09:03] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:powershell
[07/02/2020 19:09:03] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:node
[07/02/2020 19:09:03] Building host: startup suppressed: 'False', configuration suppressed: 'False', startup operation id: '32c7ec8d-454e-4421-a96e-23a9b1f10543'
[07/02/2020 19:09:03] Reading host configuration file '/Users/james/Desktop/tweet-processor/host.json'
[07/02/2020 19:09:03] Host configuration file read:
[07/02/2020 19:09:03] {
[07/02/2020 19:09:03]   "version": "2.0",
[07/02/2020 19:09:03]   "extensionBundle": {
[07/02/2020 19:09:03]     "id": "Microsoft.Azure.Functions.ExtensionBundle",
[07/02/2020 19:09:03]     "version": "[1.*, 2.0.0)"
[07/02/2020 19:09:03]   }
[07/02/2020 19:09:03] }
[07/02/2020 19:09:03] Reading functions metadata
[07/02/2020 19:09:03] 1 functions found
[07/02/2020 19:09:03] Looking for extension bundle Microsoft.Azure.Functions.ExtensionBundle at /var/folders/gk/hvm5yv5548d1t06gwbh7cbch0000gn/T/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle
[07/02/2020 19:09:03] Found a matching extension bundle at /var/folders/gk/hvm5yv5548d1t06gwbh7cbch0000gn/T/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/1.1.1
[07/02/2020 19:09:03] Fetching information on versions of extension bundle Microsoft.Azure.Functions.ExtensionBundle available on https://functionscdn.azureedge.net/public/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/index.json
[07/02/2020 19:09:04] Skipping bundle download since it already exists at path /var/folders/gk/hvm5yv5548d1t06gwbh7cbch0000gn/T/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/1.1.1
[07/02/2020 19:09:04] Loading Extention bundle from /var/folders/gk/hvm5yv5548d1t06gwbh7cbch0000gn/T/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/1.1.1
[07/02/2020 19:09:04] Initializing Warmup Extension.
[07/02/2020 19:09:04] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:java
[07/02/2020 19:09:04] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:powershell
[07/02/2020 19:09:04] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:node
[07/02/2020 19:09:04] Initializing Host. OperationId: '32c7ec8d-454e-4421-a96e-23a9b1f10543'.
[07/02/2020 19:09:04] Host initialization: ConsecutiveErrors=0, StartupCount=1, OperationId=32c7ec8d-454e-4421-a96e-23a9b1f10543
[07/02/2020 19:09:04] LoggerFilterOptions
[07/02/2020 19:09:04] {
[07/02/2020 19:09:04]   "MinLevel": "None",
[07/02/2020 19:09:04]   "Rules": [
[07/02/2020 19:09:04]     {
[07/02/2020 19:09:04]       "ProviderName": null,
[07/02/2020 19:09:04]       "CategoryName": null,
[07/02/2020 19:09:04]       "LogLevel": null,
[07/02/2020 19:09:04]       "Filter": "b__0"
[07/02/2020 19:09:04]     },
[07/02/2020 19:09:04]     {
[07/02/2020 19:09:04]       "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider",
[07/02/2020 19:09:04]       "CategoryName": null,
[07/02/2020 19:09:04]       "LogLevel": "None",
[07/02/2020 19:09:04]       "Filter": null
[07/02/2020 19:09:04]     },
[07/02/2020 19:09:04]     {
[07/02/2020 19:09:04]       "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider",
[07/02/2020 19:09:04]       "CategoryName": null,
[07/02/2020 19:09:04]       "LogLevel": null,
[07/02/2020 19:09:04]       "Filter": "b__0"
[07/02/2020 19:09:04]     }
[07/02/2020 19:09:04]   ]
[07/02/2020 19:09:04] }
[07/02/2020 19:09:04] FunctionResultAggregatorOptions
[07/02/2020 19:09:04] {
[07/02/2020 19:09:04]   "BatchSize": 1000,
[07/02/2020 19:09:04]   "FlushTimeout": "00:00:30",
[07/02/2020 19:09:04]   "IsEnabled": true
[07/02/2020 19:09:04] }
[07/02/2020 19:09:04] SingletonOptions
[07/02/2020 19:09:04] {
[07/02/2020 19:09:04]   "LockPeriod": "00:00:15",
[07/02/2020 19:09:04]   "ListenerLockPeriod": "00:00:15",
[07/02/2020 19:09:04]   "LockAcquisitionTimeout": "10675199.02:48:05.4775807",
[07/02/2020 19:09:04]   "LockAcquisitionPollingInterval": "00:00:05",
[07/02/2020 19:09:04]   "ListenerLockRecoveryPollingInterval": "00:01:00"
[07/02/2020 19:09:04] }
[07/02/2020 19:09:04] HttpOptions
[07/02/2020 19:09:04] {
[07/02/2020 19:09:04]   "DynamicThrottlesEnabled": false,
[07/02/2020 19:09:04]   "MaxConcurrentRequests": -1,
[07/02/2020 19:09:04]   "MaxOutstandingRequests": -1,
[07/02/2020 19:09:04]   "RoutePrefix": "api"
[07/02/2020 19:09:04] }
[07/02/2020 19:09:04] Starting JobHost
[07/02/2020 19:09:04] Starting Host (HostId=jamessmacbookpro-180331641, InstanceId=773e4720-335c-4004-998f-925b1844edff, Version=3.0.13107, ProcessId=39553, AppDomainId=1, InDebugMode=False, InDiagnosticMode=False, FunctionsExtensionVersion=(null))
[07/02/2020 19:09:04] Loading functions metadata
[07/02/2020 19:09:04] 1 functions loaded
[07/02/2020 19:09:04] Loading proxies metadata
[07/02/2020 19:09:04] Initializing Azure Function proxies
[07/02/2020 19:09:05] 0 proxies loaded
[07/02/2020 19:09:05] Starting worker process:python  /Users/james/.vscode/extensions/ms-python.python-2020.1.58038/pythonFiles/ptvsd_launcher.py --default --host <IP_ADDRESS> --port 9091 --wait<EMAIL_ADDRESS>--host <IP_ADDRESS> --port 52683 --workerId 83196165-a803-4b90-ae8f-0cf2beda7ab1 --requestId 181bc73d-f267-4f18-a631-18d94bf33bc6 --grpcMaxMessageLength 134217728
[07/02/2020 19:09:05] python process with Id=39558 started
[07/02/2020 19:09:05] Generating 1 job function(s)
[07/02/2020 19:09:05] Found the following functions:
[07/02/2020 19:09:05] Host.Functions.poll_process_store
[07/02/2020 19:09:05]
[07/02/2020 19:09:05] Initializing function HTTP routes
[07/02/2020 19:09:05] No HTTP routes mapped
[07/02/2020 19:09:05]
[07/02/2020 19:09:05] Host initialized (631ms)
[07/02/2020 19:09:05] Executing 'Functions.poll_process_store' (Reason='Timer fired at 2020-02-07T19:09:05.7646830+00:00', Id=e12da748-edea-487d-a9a4-5704f0e01107)
[07/02/2020 19:09:05] Trigger Details: UnscheduledInvocationReason: IsPastDue, OriginalSchedule: 2020-02-06T11:11:00.0000000+00:00
[07/02/2020 19:10:05] Starting worker process failed
[07/02/2020 19:10:05] The operation has timed out.
[07/02/2020 19:10:05] Starting worker process:python  /Users/james/.vscode/extensions/ms-python.python-2020.1.58038/pythonFiles/ptvsd_launcher.py --default --host <IP_ADDRESS> --port 9091 --wait<EMAIL_ADDRESS>--host <IP_ADDRESS> --port 52683 --workerId 3001fb65-2374-451a-81f6-b8e177c9b26b --requestId 2a11ca3c-42ac-48a0-baaf-ed72298e1b96 --grpcMaxMessageLength 134217728
[07/02/2020 19:10:05] python process with Id=39567 started
[07/02/2020 19:10:05] Executed 'Functions.poll_process_store' (Failed, Id=e12da748-edea-487d-a9a4-5704f0e01107)
[07/02/2020 19:10:05] System.Private.CoreLib: Exception while executing function: Functions.poll_process_store. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[07/02/2020 19:10:05] The next 5 occurrences of the 'poll_process_store' schedule (Cron: '0 * * * * *') will be:
[07/02/2020 19:10:05] 02/07/2020 19:11:00+00:00 (02/07/2020 19:11:00Z)
[07/02/2020 19:10:05] 02/07/2020 19:12:00+00:00 (02/07/2020 19:12:00Z)
[07/02/2020 19:10:05] 02/07/2020 19:13:00+00:00 (02/07/2020 19:13:00Z)
[07/02/2020 19:10:05] 02/07/2020 19:14:00+00:00 (02/07/2020 19:14:00Z)
[07/02/2020 19:10:05] 02/07/2020 19:15:00+00:00 (02/07/2020 19:15:00Z)
[07/02/2020 19:10:05]
[07/02/2020 19:10:05] Executing 'Functions.poll_process_store' (Reason='Timer fired at 2020-02-07T19:10:05.3169880+00:00', Id=5c5b59c3-940b-4ab8-98af-7140dfa25f86)
[07/02/2020 19:10:05] Executed 'Functions.poll_process_store' (Failed, Id=5c5b59c3-940b-4ab8-98af-7140dfa25f86)
[07/02/2020 19:10:05] System.Private.CoreLib: Exception while executing function: Functions.poll_process_store. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[07/02/2020 19:10:05] Host started (60664ms)
[07/02/2020 19:10:05] Job host started
Hosting environment: Production
Content root path: /Users/james/Desktop/tweet-processor
Now listening on: http://<IP_ADDRESS>:7071
Application started. Press Ctrl+C to shut down.
[07/02/2020 19:10:10] Host lock lease acquired by instance ID '0000000000000000000000007B947751'.
[07/02/2020 19:11:00] Executing 'Functions.poll_process_store' (Reason='Timer fired at 2020-02-07T19:11:00.0011840+00:00', Id=b1e62813-bd31-4154-8d0a-52f605abf0e3)
[07/02/2020 19:11:00] Executed 'Functions.poll_process_store' (Failed, Id=b1e62813-bd31-4154-8d0a-52f605abf0e3)
[07/02/2020 19:11:00] System.Private.CoreLib: Exception while executing function: Functions.poll_process_store. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[07/02/2020 19:11:05] Starting worker process failed
[07/02/2020 19:11:05] The operation has timed out.
[07/02/2020 19:11:05] Starting worker process:python  /Users/james/.vscode/extensions/ms-python.python-2020.1.58038/pythonFiles/ptvsd_launcher.py --default --host <IP_ADDRESS> --port 9091 --wait<EMAIL_ADDRESS>--host <IP_ADDRESS> --port 52683 --workerId 62addb16-f80f-4aaa-9310-1df7ce88e371 --requestId 5893e098-9549-4912-8003-94f124b9bb67 --grpcMaxMessageLength 134217728
[07/02/2020 19:11:05] python process with Id=39575 started
[07/02/2020 19:12:00] Executing 'Functions.poll_process_store' (Reason='Timer fired at 2020-02-07T19:12:00.0035930+00:00', Id=98964db6-cb85-470d-ac1e-6d43459949c2)
[07/02/2020 19:12:00] Executed 'Functions.poll_process_store' (Failed, Id=98964db6-cb85-470d-ac1e-6d43459949c2)
[07/02/2020 19:12:00] System.Private.CoreLib: Exception while executing function: Functions.poll_process_store. Microsoft.Azure.WebJobs.Script: Did not find any initialized language workers.
[07/02/2020 19:12:05] Starting worker process failed
[07/02/2020 19:12:05] The operation has timed out.
[07/02/2020 19:12:05] Exceeded language worker restart retry count for runtime:python. Shutting down Functions Host
[07/02/2020 19:12:05] Stopping host...
[07/02/2020 19:12:05] Stopping JobHost
[07/02/2020 19:12:05] Job host stopped
[07/02/2020 19:12:05] Host shutdown completed.
Terminal will be reused by tasks, press any key to close it.`
Let me know if I missed anything

Update: I've seen this issue sometimes for linux when LinuxFxVersion is off (or if the placeholder ID doesn't match what is expected, ex: node ~8 and e ~3).
We also need to see if there's a root cause to "The operation has timed out" or if there are more logs we can add to find a root cause.

I'm also seeing this issue on MacOS. I haven't tried it on Windows. It's happening for both new and existing project. My venv is using Python 3.7.5.
It runs fine if I try to run using func start at the commandline, but then I can attach vs code to debug that running instance.

@cecilphillip - we've been looking for a consistent repro!! Do you mean that it fails when you F5 debug with the default VS Code task? And could you send us what that configuration looks like (or the whole project if that's alright!). Thanks!

Thanks @cecilphillip for the repo.
Could you check if your Python 3.7 interpreter is 32-bit or 64-bit?
e.g. when you type python in your command line
Python 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 24 2018, 00:16:47) **[MSC v.1916 64 bit (AMD64)]** on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>

In the virtual environment it looks like this on MacOS. I'm not sure what that means in terms of the bitness
Python 3.7.5 (default, Dec  7 2019, 19:13:15)
[Clang 10.0.1 (clang-1<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

@cecilphillip spent some time looking into this (thank you!) and we found that using the local storage emulator (mac only, "AzureWebJobsStorage": "UseDevelopmentStorage=true") caused intermittent issues. Believed to be related to this: https://github.com/Azure/azure-functions-core-tools/issues/1247
It's still odd that the right errors weren't shown for this issue. I think this issue should track that missing error output (cc: @Hazhzeng )

I ran the same code inside of a vscode remote container based on their Functions/Python template and I'm not getting these errors there.
For me, this seems to be a MacOS specific issue....

No it's not MacOS specific. I get this way to often in Debian too.

After being stuck the entire afternoon with this bug I cloned a new version of my build tree. Now it worked at the first try. Could it be possible that something in my .venv or .vscode has been corrupted?

Now it's back again. I still haven't figured out what's causing this.

@petterj - are you using Azurite? And do you mind posting logs of a non-working instance (logs start => error)

Is there a workaround for this? For example, how can i tell if i'm using Azurite? And if i am, how can i switch from it?

I'm also having this issue. When I run func host start it works, however when I use the F5 debug mode I get:
python process with Id=xxxxx started
Starting worker process failed
The operation has timed out.
I'm running python 3.7.5 64 bit on Windows.
My function is using a service bus trigger.
I'm not using a local storage emulator.
Is there any fix for this? It seems like it's happening fairly regularly for people.

@JB-NZ - when you run and it times out, can you send me the log line starting with Starting worker process:python?
Example
/home/mhoeger/.vscode/extensions/ms-python.python-2020.3.69010/pythonFiles/lib/python/debugpy/no_wheels/debugpy --listen <IP_ADDRESS>:9091 --wait-for-client "/usr/lib/azure-functions-core-tools/workers/python/3.7/LINUX/X64/worker.py" --host <IP_ADDRESS> --port 44227 --workerId f78f20fb-f48c-4ff8-baf7-54fbe02ba968 --requestId a11a685c-1da8-4703-bbb9-1fdabed2b5b0 --grpcMaxMessageLength 134217728
Same with when it's working (working with F5)

@mhoeger I have never had this function working with the debugger (F5), I always get the issue with starting the worker process.  Can anyone please help me with this?

Hey @EricJizbaMSFT - from what I've been able to see, this seems like a VS Code issue (process gets started pointing to python code from ms-python, stalls, never hits Azure Functions Python Worker code). I'm not sure if the underlying issue is in your domain or more with ms-python, but can you help investigate?

@mhoeger is there a consistent repro? I don't think I've ever seen this happen.
Most of this experience is controlled by the func cli and the python extension. We mostly just call this api to get the debug arguments and pass them along to the func cli

No, it comes and goes. I haven’t figured out when.
Once it’s in this state it happens all the time.
Checking out a fresh build tree (with my code staying exactly the same) usually helps. Last time I tried to run the “func host start” manually and then the problem fixed itself aswell even for starting from VS Code.
Someone isn’t cleaning up things properly. Might be that I have an unseen bug in my code (!?). But I still think the dev environment should be able to cope.
Skickat från min iPhone
23 apr. 2020 kl. 23:19 skrev Eric Jizba <notifications<EMAIL_ADDRESS>@mhoegerhttps://github.com/mhoeger is there a consistent repro? I don't think I've ever seen this happen.
Most of this experience is controlled by the func cli and the python extension. We mostly just call this apihttps://github.com/microsoft/vscode-python/blob/master/src/client/api.ts#L35 to get the debug arguments and pass them along to the func cli
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-functions-python-worker/issues/607#issuecomment-618677861, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AO3WID4LGETNLK4BJNIXZXTROCWHLANCNFSM4KG3HMMQ.

I'm seeing this a lot more having upgraded from azure-functions-core-tools to azure-functions-core-tools-3

Trying to run a python azure function locally using VSCode, but  it keeps shutting down
Trying to run a python azure function locally using VSCode, but  it keeps shutting down with below errors,
[27/05/2020 01:18:30] Starting worker process failed
[27/05/2020 01:18:30] The operation has timed out.
Found Python version 3.7.6 (python3).
              %%%%%%
             %%%%%%
        @   %%%%%%    @
      @@   %%%%%%      @@
   @@@    %%%%%%%%%%%    @@@
 @@      %%%%%%%%%%        @@
   @@         %%%%       @@
     @@      %%%       @@
       @@    %%      @@
            %%
            %

Azure Functions Core Tools (2.7.2508 Commit hash: 4da36643c32783a832094318afcd679fa9d76455)
Function Runtime Version: 2.0.13351.0
AZURE_FUNCTIONS_ENVIRONMENT: Development
[27/05/2020 01:15:26] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:java
[27/05/2020 01:15:26] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:powershell
[27/05/2020 01:15:26] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:node
[27/05/2020 01:15:26] Building host: startup suppressed: 'False', configuration suppressed: 'False', startup operation id: '5c6099b3-f738-4f74-9617-0ede842e2a1c'
[27/05/2020 01:15:26] Reading host configuration file '/Users/umeshraghavan/Documents/Python_Learning/Azure_Test/host.json'
[27/05/2020 01:15:26] Host configuration file read:
[27/05/2020 01:15:26] {
[27/05/2020 01:15:26]   "version": "2.0",
[27/05/2020 01:15:26]   "extensionBundle": {
[27/05/2020 01:15:26]     "id": "Microsoft.Azure.Functions.ExtensionBundle",
[27/05/2020 01:15:26]     "version": "[1.*, 2.0.0)"
[27/05/2020 01:15:26]   }
[27/05/2020 01:15:26] }
[27/05/2020 01:15:26] Reading functions metadata
[27/05/2020 01:15:26] 1 functions found
[27/05/2020 01:15:26] Looking for extension bundle Microsoft.Azure.Functions.ExtensionBundle at /var/folders/z0/ps9_z2zd7vq1dgdp1q23sb5r0000gn/T/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle
[27/05/2020 01:15:27] Found a matching extension bundle at /var/folders/z0/ps9_z2zd7vq1dgdp1q23sb5r0000gn/T/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/1.1.1
[27/05/2020 01:15:27] Fetching information on versions of extension bundle Microsoft.Azure.Functions.ExtensionBundle available on https://functionscdn.azureedge.net/public/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/index.json
[27/05/2020 01:15:27] Skipping bundle download since it already exists at path /var/folders/z0/ps9_z2zd7vq1dgdp1q23sb5r0000gn/T/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/1.1.1
[27/05/2020 01:15:27] Loading Extention bundle from /var/folders/z0/ps9_z2zd7vq1dgdp1q23sb5r0000gn/T/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/1.1.1
[27/05/2020 01:15:27] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:java
[27/05/2020 01:15:27] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:powershell
[27/05/2020 01:15:27] FUNCTIONS_WORKER_RUNTIME set to python. Skipping WorkerConfig for language:node
[27/05/2020 01:15:28] Initializing Warmup Extension.
[27/05/2020 01:15:28] Initializing Host. OperationId: '5c6099b3-f738-4f74-9617-0ede842e2a1c'.
[27/05/2020 01:15:28] Host initialization: ConsecutiveErrors=0, StartupCount=1, OperationId=5c6099b3-f738-4f74-9617-0ede842e2a1c
[27/05/2020 01:15:28] LoggerFilterOptions
[27/05/2020 01:15:28] {
[27/05/2020 01:15:28]   "MinLevel": "None",
[27/05/2020 01:15:28]   "Rules": [
[27/05/2020 01:15:28]     {
[27/05/2020 01:15:28]       "ProviderName": null,
[27/05/2020 01:15:28]       "CategoryName": null,
[27/05/2020 01:15:28]       "LogLevel": null,
[27/05/2020 01:15:28]       "Filter": "b__0"
[27/05/2020 01:15:28]     },
[27/05/2020 01:15:28]     {
[27/05/2020 01:15:28]       "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider",
[27/05/2020 01:15:28]       "CategoryName": null,
[27/05/2020 01:15:28]       "LogLevel": "None",
[27/05/2020 01:15:28]       "Filter": null
[27/05/2020 01:15:28]     },
[27/05/2020 01:15:28]     {
[27/05/2020 01:15:28]       "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider",
[27/05/2020 01:15:28]       "CategoryName": null,
[27/05/2020 01:15:28]       "LogLevel": null,
[27/05/2020 01:15:28]       "Filter": "b__0"
[27/05/2020 01:15:28]     }
[27/05/2020 01:15:28]   ]
[27/05/2020 01:15:28] }
[27/05/2020 01:15:28] FunctionResultAggregatorOptions
[27/05/2020 01:15:28] {
[27/05/2020 01:15:28]   "BatchSize": 1000,
[27/05/2020 01:15:28]   "FlushTimeout": "00:00:30",
[27/05/2020 01:15:28]   "IsEnabled": true
[27/05/2020 01:15:28] }
[27/05/2020 01:15:28] SingletonOptions
[27/05/2020 01:15:28] {
[27/05/2020 01:15:28]   "LockPeriod": "00:00:15",
[27/05/2020 01:15:28]   "ListenerLockPeriod": "00:00:15",
[27/05/2020 01:15:28]   "LockAcquisitionTimeout": "10675199.02:48:05.4775807",
[27/05/2020 01:15:28]   "LockAcquisitionPollingInterval": "00:00:05",
[27/05/2020 01:15:28]   "ListenerLockRecoveryPollingInterval": "00:01:00"
[27/05/2020 01:15:28] }
[27/05/2020 01:15:28] HttpOptions
[27/05/2020 01:15:28] {
[27/05/2020 01:15:28]   "DynamicThrottlesEnabled": false,
[27/05/2020 01:15:28]   "MaxConcurrentRequests": -1,
[27/05/2020 01:15:28]   "MaxOutstandingRequests": -1,
[27/05/2020 01:15:28]   "RoutePrefix": "api"
[27/05/2020 01:15:28] }
[27/05/2020 01:15:28] Starting JobHost
[27/05/2020 01:15:28] Starting Host (HostId=1921681109-1141020319, InstanceId=b8d55010-7661-490f-a07c-8fa69ffc3a8f, Version=2.0.13351.0, ProcessId=86746, AppDomainId=1, InDebugMode=False, InDiagnosticMode=False, FunctionsExtensionVersion=(null))
[27/05/2020 01:15:28] Loading functions metadata
[27/05/2020 01:15:28] 1 functions loaded
[27/05/2020 01:15:28] Loading proxies metadata
[27/05/2020 01:15:28] Initializing Azure Function proxies
[27/05/2020 01:15:29] 0 proxies loaded
[27/05/2020 01:15:29] Starting worker process:python3  /Users/umeshraghavan/.vscode/extensions/ms-python.python-2020.5.80290/pythonFiles/lib/python/debugpy/no_wheels/debugpy --listen <IP_ADDRESS>:9091 --wait-for-client "/usr/local/Cellar/azure-functions-core-tools/2.7.2508/workers/python/3.7/OSX/X64/worker.py" --host <IP_ADDRESS> --port 53389 --workerId 0c30d5db-7c6c-4969-8242-841bb3ef834c --requestId 25d1722e-a751-4cff-bb9d-274e02d05475 --grpcMaxMessageLength 134217728
[27/05/2020 01:15:29] python3 process with Id=86750 started
[27/05/2020 01:15:29] Generating 1 job function(s)
[27/05/2020 01:15:29] Found the following functions:
[27/05/2020 01:15:29] Host.Functions.HttpTrigger1
[27/05/2020 01:15:29]
[27/05/2020 01:15:30] Initializing function HTTP routes
[27/05/2020 01:15:30] Mapped function route 'api/HttpTrigger1' [get,post] to 'HttpTrigger1'
[27/05/2020 01:15:30]
[27/05/2020 01:15:30] Host initialized (1601ms)
[27/05/2020 01:15:30] Host started (1674ms)
[27/05/2020 01:15:30] Job host started
Hosting environment: Development
Content root path: /Users/umeshraghavan/Documents/Python_Learning/Azure_Test
Now listening on: http://<IP_ADDRESS>:7071
Application started. Press Ctrl+C to shut down.
Http Functions:
    HttpTrigger1: [GET,POST] http://localhost:7071/api/HttpTrigger1

[27/05/2020 01:15:35] Host lock lease acquired by instance ID '000000000000000000000000DAAA6D0A'.
[27/05/2020 01:16:29] Starting worker process failed
[27/05/2020 01:16:29] The operation has timed out.
[27/05/2020 01:16:30] Starting worker process:python3  /Users/umeshraghavan/.vscode/extensions/ms-python.python-2020.5.80290/pythonFiles/lib/python/debugpy/no_wheels/debugpy --listen <IP_ADDRESS>:9091 --wait-for-client "/usr/local/Cellar/azure-functions-core-tools/2.7.2508/workers/python/3.7/OSX/X64/worker.py" --host <IP_ADDRESS> --port 53389 --workerId 945c9b17-5aa1-4fbe-8e6c-6f9a44fde0c4 --requestId 4be76ccb-17a0-422b-9107-e5ddeb178f82 --grpcMaxMessageLength 134217728
[27/05/2020 01:16:30] python3 process with Id=86763 started
[27/05/2020 01:17:30] Starting worker process failed
[27/05/2020 01:17:30] The operation has timed out.
[27/05/2020 01:17:30] Starting worker process:python3  /Users/umeshraghavan/.vscode/extensions/ms-python.python-2020.5.80290/pythonFiles/lib/python/debugpy/no_wheels/debugpy --listen <IP_ADDRESS>:9091 --wait-for-client "/usr/local/Cellar/azure-functions-core-tools/2.7.2508/workers/python/3.7/OSX/X64/worker.py" --host <IP_ADDRESS> --port 53389 --workerId febbee78-f46c-4817-8a4a-e594f5790885 --requestId bb5da0ce-998e-4599-bdb3-7f0198397eac --grpcMaxMessageLength 134217728
[27/05/2020 01:17:30] python3 process with Id=86773 started
[27/05/2020 01:18:30] Starting worker process failed
[27/05/2020 01:18:30] The operation has timed out.
[27/05/2020 01:18:30] Exceeded language worker restart retry count for runtime:python. Shutting down Functions Host
[27/05/2020 01:18:30] Stopping host...
[27/05/2020 01:18:30] Stopping JobHost
[27/05/2020 01:18:30] Job host stopped
[27/05/2020 01:18:30] Host shutdown completed.
Application is shutting down...

This is so interesting,
at [27/05/2020 01:15:29] python3 process with Id=86750 started
The Python process already started.
After [27/05/2020 01:15:35] Host lock lease acquired by instance ID '000000000000000000000000DAAA6D0A'., we should expect to see INFO: Starting Azure Functions Python Worker. and INFO: Worker ID: 99c82197-7993-4981-998f-0da4d87fc442, Request ID: 0ea7e618-4e72-487d-9796-252a27888884, Host Address: <IP_ADDRESS>:41155 from the Python worker.
Instead, we see the error message [27/05/2020 01:16:29] Starting worker process failed after Host lock lease acquired.
@mhoeger, could it be possible that there's a race condition between python3 process with Id=86763 started and Host lock lease acquired?

@Hazhzeng - The host lock lease acquisition is independent of the worker process starting, so that wouldn't be the issue :\ As far as we've been able to tell, there's some issue (likely race condition) with the "F5" debug experience of starting a function locally, but not with "func host start".
@JB-NZ or others, do you have a project you could make public that is showing this behavior? Or does it happen even in the most basic cases (suggesting it's something to do with the environment configuration)?

Hi @umeshraghavan, thanks for sharing the log.
One question, since the log shows The operation has timed out, does this issue fail quickly (like after 1 minute)? Or does it fail immediately?

It’s not even consistent within a project. But when it does happen the only way to release it (on a Mac) is to reboot. It never times out, you can’t kill the process, and if you close vs code the process becomes orphaned and unkillable.

Hi @Hazhzeng , yes it was failing immediately.

@Hazhzeng - The host lock lease acquisition is independent of the worker process starting, so that wouldn't be the issue :\ As far as we've been able to tell, there's some issue (likely race condition) with the "F5" debug experience of starting a function locally, but not with "func host start".
@JB-NZ or others, do you have a project you could make public that is showing this behavior? Or does it happen even in the most basic cases (suggesting it's something to do with the environment configuration)?

I encountered this issue with a very basic HTTP trigger function just now, running VS code on Windows. But it worked like a charm running "func host start" in powershell.

VS code version:
Version: 1.46.0 (user setup)
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-10T09:03:20.462Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

So far, I can give a summary for what vscode F5 does:

It goes to the launch.json, and execute the prelaunch task "func: host start" provided by vscode-azurefunctions extension.
The vscode-azurefunctions extension inject the languageWorkers__python__arguments environment variable into the azure-functions-host. (extension code here)
The azure-functions-host will now replace the Python worker execution command with the one set in languageWorkers__python__arguments. For example, languageWorkers__python__arguments = python  /home/hazeng/.vscode/extensions/ms-python.python-2020.5.86806/pythonFiles/lib/python/debugpy/no_wheels/debugpy --listen <IP_ADDRESS>:9091 --wait-for-client "/usr/lib/node_modules/azure-functions-core-tools/bin/workers/python/3.7/LINUX/X64/worker.py" --host <IP_ADDRESS> --port 36779 --workerId 0418316d-1c26-473a-bef8-db10134d0a0e --requestId 4cb4f2e7-5ab1-473e-8ccd-0bca60789db2 --grpcMaxMessageLength 134217728.

The python is the interpreter executable that the host will use to execute the debug service.
The debugpy --listen <IP_ADDRESS>:9091 will create a debug server on 9091 port. The  debugpy --wait-for-client means that the worker code should not run until VSCode is connected to the debug server.
The LINUX/X64/worker.py --host <IP_ADDRESS> --port 36779 will create a Azure Functions Python Worker with a GRPC channel, serving at 36779 port.

Once the Python interpreter starts, the azure-functions-host will report python process with Id=83728 started. (host code here)
Now the azure-functions-host will register the process (host code here), waiting for the worker to acknowledge the host with StartStream request (host code here) (worker code here).

The chain of execution is:
VSCode F5 => vscode-extension => azure-functions-host => python interpreter => ms.python debugpy => azure-functions-python worker.py.
So, if this issue occurs immediately, and showing:

python process with Id=83728 started
Starting worker process failed
The operation has timed out

I suspect it is the --wait-for-client argument presents on debugpy. This will block the worker.py code starting until the VSCode debug client connects to it. Meanwhile, azure-functions-host may get a timeout when waiting for StartStream request from the worker process as it never gets started. Any suggestions, @EricJizbaMSFT @mhoeger?
By the way, if @fisherjames have a consistent repro, could you trim the project off all sensitive information, and share it with us? That would greatly speed up our investigation.

I found that it was possible to get rid of the problem by cloning another instance of the same repo. It worked for a while before the problem was back again.
Are there any temporary files written after pressing F5?
Skickat från min iPhone
11 juni 2020 kl. 08:02 skrev Rob Aleck<EMAIL_ADDRESS>
It’s not even consistent within a project. But when it does happen the only way to release it (on a Mac) is to reboot. It never times out, you can’t kill the process, and if you close vs code the process becomes orphaned and unkillable.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-functions-python-worker/issues/607#issuecomment-642427418, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AO3WIDZY7NBJH6PQZETHJODRWBXNPANCNFSM4KG3HMMQ.

After discussing with @mhoeger offline, we notice that the vscode-azurefunctions extension will not attach to the host process until Host lock lease acquired by instance ID is found (code)[https://github.com/microsoft/vscode-azurefunctions/blob/6f0e9d987ecfd17f1317e4af475f1839f8406a3b/package.json#L780-L794].
In Python case, the host emits the message Host lock lease acquired by instance ID when the Python interpreter starts. But the Python interpreter does NOT ignite the Python worker script directly, it starts the debugpy process first.
So, I think this issue is caused by

The Python interpreter starts and loads the debugpy module (Python worker not yet started, --wait-for-client flag)
The host emits Host lock lease acquired by instance ID message
The VSCode Azure Functions Extension finishes in func-watch. As func: host start preLaunchTask is finished, now VSCode pass the control to ms.python extension for debugging.
The VSCode debugger client attempts to attach to the debugpy server, however, since Python worker is not yet started, source code is not found, which causes the main Python interpreter process to fail immediately.
Since the main Python interpreter process exit, the host throws an exception Starting worker process failed.

the Starting worker process failed error never happens. If you get this error, the processes are successfully terminated and you can retry.

it'd be good if there was some detailed debug logging that we could share - on a mac, where can i find this?

This is related to the issue https://github.com/Azure/azure-functions-host/issues/4384

Having this issue now - is there a way to use this code as is? Or when is it scheduled for release?

The latest Azure Functions VSCode extension should have the fix for this issue. Please update to the latest version. Thanks.

@Hazhzeng I'm still having this issue, same symptoms as above. I've stripped my code down to "Hello World" and it still is an issue. However, if I create a new folder, it works fine:

Executing task: .venv\Scripts\python -m pip install -r requirements.txt <

Requirement already satisfied: azure-functions in c:\users\andrew.velez\source\repos\azfnsql.venv\lib\site-packages (from -r requirements.txt (line 5)) (1.3.0)
WARNING: You are using pip version 20.1.1; however, version 20.2.2 is available.
You should consider upgrading via the 'C:\Users\andrew.velez\source\repos\AzFnSql.venv\Scripts\python.exe -m pip install --upgrade pip' command.
Terminal will be reused by tasks, press any key to close it.

Executing task: .venv\Scripts\activate ; func host start <

Found Python version 3.7.8 (py).
Azure Functions Core Tools (2.7.2855 Commit hash: 674ea7a0dd605e6c61349839129596841c1a8f30)
Function Runtime Version: 2.0.14248.0
AZURE_FUNCTIONS_ENVIRONMENT: Development
Hosting environment: Development
Content root path: C:\Users\andrew.velez\source\repos\AzFnSql
Now listening on: http://<IP_ADDRESS>:7071
Application started. Press Ctrl+C to shut down.
Functions:
    TestConnection: [GET,POST] http://localhost:7071/api/TestConnection

For detailed output, run func with --verbose flag.
Starting worker process failed
The operation has timed out.

Identical problem as @andrew-velez-trusight . Completely unable to start applications locally on MacOS running latest version of Core Tools and Functions.

I had the same problem. I'm building a function triggered by timer, and I found that trying to trigger it every minute cause the debugger to fail with "Starting worker process failed". Change the scheduling to 5 minutesin function.json: "schedule": "0 */5 * * * *" and it seems to work now

I have the same problem and cannot figure out how to fix it.

I'm still seeing this error too. Everything was rock solid (multiple functions with http triggers) during development over the last few weeks, but as soon as I added a function with a service bus trigger I could no longer use F5 to launch the project. Using func host start works fine.
What's feels slightly odd is that it looks like everything is running ok until the operation times out with the Starting worker process failed error. If any of the functions  are invoked, it just shows the "Executing..." message, but hangs without executing the function.

Not sure if it's relevant, but maybe it will help somebody.
I was running into the same issue with a serviceBusTrigger and python 3.8.6.
Turned out my storage emulator wasn't running and I had "AzureWebJobsStorage": "UseDevelopmentStorage=true".
I started it and now it works OK.
Mine issue looked like this:
[2020-12-05T12:35:54.847Z] Executing 'Functions.test' (Reason='New ServiceBus message detected on 'test'.', Id=1bcec3cf-533f-41af-a6c3-bfe336c97cd8)
[2020-12-05T12:35:54.849Z] Trigger Details: MessageId: a0f127a42a884cdc91aea4ca7695a4c9, DeliveryCount: 1, EnqueuedTime: 12/5/2020 12:35:54 PM, LockedUntil: 12/5/2020 12:36:24 PM, SessionId: (null)
[2020-12-05T12:36:14.890Z] Starting worker process failed
[2020-12-05T12:36:14.894Z] The operation has timed out.
[2020-12-05T12:37:14.955Z] Starting worker process failed
[2020-12-05T12:37:14.976Z] The operation has timed out.
[2020-12-05T12:38:15.015Z] Starting worker process failed
[2020-12-05T12:38:15.018Z] The operation has timed out.
[2020-12-05T12:38:15.024Z] Exceeded language worker restart retry count for runtime:python. Shutting down and proactively recycling the Functions Host to recover
[2020-12-05T12:38:15.033Z] Stopping host...
[2020-12-05T12:38:15.040Z] Stopping JobHost
[2020-12-05T12:38:15.043Z] Stopping the listener 'Microsoft.Azure.WebJobs.ServiceBus.Listeners.ServiceBusListener' for function 'deals-poc'
[2020-12-05T12:38:15.056Z] Stopped the listener 'Microsoft.Azure.WebJobs.ServiceBus.Listeners.ServiceBusListener' for function 'deals-poc'
[2020-12-05T12:38:15.059Z] Job host stopped
[2020-12-05T12:38:15.062Z] Host shutdown completed.

Getting this also. Why is this issue closed? Is there a new issue we should be following.
For me running func start works from the command line, but VS Code is totally to start the Azure python function itself. Eventually giving up with :Starting worker process failed. The operation has timed out"

@dirkesquire, I just reverted to Azure Functions version 1.0.0 in VS Code and am able to debug now.
@Hazhzeng please reopen this issue, this is not fixed in version 1.1.0.

I spoke too soon, reverting to a previous version only worked one time.

Hi all - the bug is in the https://github.com/microsoft/vscode-azurefunctions repo and is being fixed there by @Hazhzeng: https://github.com/microsoft/vscode-azurefunctions/pull/2576
A complete resolution to the issue is being tracked here: https://github.com/microsoft/vscode-azurefunctions/issues/781
Before this fix, there was also a mitigation put in place by the VS Code Extension to stop func task post debug by default ("azureFunctions.stopFuncTaskPostDebug": true in .vscode/settings.json). However, I think that there is still a chance where the spun up debug python process from a previous debug session is not killed correctly? If you run into this issue, please try killing all python.exe processes before starting to debug again (as a workaround).

@mhoeger the issue and PR you mentioned are specific to editing Python files while debugging. Based on the above comments, I thought people were struggling to get debugging to work in the first place. If that's the case, I'm happy to have people file a new issue on our VS Code repo with their exact repro steps. This issue has too many separate scenarios/workarounds going on. It's a very generic error that could be caused by a variety of different things, requiring a variety of different solutions.

Thank you @mhoeger. "azureFunctions.stopFuncTaskPostDebug": true seems to be working for me on version 1.1.0.

@ejizba - my understanding of the fix is that setting "wait for client" to false will make sure that the python worker code has a chance to execute, regardless of whether or not the debugger has or will start? If this understanding is true, I think "The operation has timed out" issue won't show up anymore (since it was caused by worker code never executing).

I had the same problem. I'm building a function triggered by timer, and I found that trying to trigger it every minute cause the debugger to fail with "Starting worker process failed". Change the scheduling to 5 minutesin function.json: "schedule": "0 */5 * * * *" and it seems to work now

Also faced this timeout again today (since December) and found this ticket. Odd thing is:

I set default logging to Warning -> timeout,
I revert it to Information -> works.

I hope this helps...

I had the same problem. I'm building a function triggered by timer, and I found that trying to trigger it every minute cause the debugger to fail with "Starting worker process failed". Change the scheduling to 5 minutesin function.json: "schedule": "0 */5 * * * *" and it seems to work now

Also faced this timeout again today (since December) and found this ticket. Odd thing is:

I set default logging to Warning -> timeout,
I revert it to Information -> works.

I hope this helps...

I also have a Timer-Trigger which I'm running in a container,  but its running only once.
What should I put in the 'Docker Compose'  to ensure I'm running the timer and NOT the script.py file ?
Docker-Compose.debug:
services:
  sfunc:
    image: sfunc
    build:
      context: .
      dockerfile: ./Dockerfile
      command: ["sh", "-c", "pip install debugpy -t /tmp && python /tmp/debugpy
            --wait-for-client --listen <IP_ADDRESS>:5678 TimerTrigger/__init__.py"]
    ports:
      - 5678:5678 ```

I also have a Timer-Trigger which I'm running in a container,  but its running only once.
What should I put in the 'Docker Compose'  to ensure I'm running the timer and NOT the script.py file ?
Docker-Compose.debug:
services:
  sfunc:
    image: sfunc
    build:
      context: .
      dockerfile: ./Dockerfile
      command: ["sh", "-c", "pip install debugpy -t /tmp && python /tmp/debugpy
            --wait-for-client --listen <IP_ADDRESS>:5678 TimerTrigger/__init__.py"]
    ports:
      - 5678:5678 ```


error composer package installer

The installation package mentioned in the readme is wrong, they should correct it with this "composer global require lara-zeus/installer"

updated the readme, thank you.


Disable "global" in vitest

I tried and ran into TS issues. Would love to ditch it though.

@kentcdodds
Can you provide the draft you are working on?
I will try to work on in

I didn't save it. There wasn't much to it. Just remove some stuff from the vitest config and the tsconfig and things stopped working 😅 I didn't spend much time on it I'm afraid.

do you want to remove:
globals from vitest.config.ts:
  plugins: [react(), tsconfigPaths()],
  test: {
    include: ['./app/**/*.test.{ts,tsx}'],
-    globals: true,
    environment: 'jsdom',
    setupFiles: ['./other/test-setup/setup-test-env.ts'],
    globalSetup: ['./other/test-setup/global-setup.ts'],

or
global from setup-test-env.ts
declare global {
  namespace Vi {
    interface JestAssertion<T = any>
      extends jest.Matchers<void, T>,
        TestingLibraryMatchers<T, void> {}
  }
}

or ...


OLP-1270: CLI for local blockchain network using docker

The the docker-compose-builder needs a mechanism to deploy smart contracts as well.
The easiest way would be to add a flag through which we can speficy a a metamask private key . Currently it picks up the key from a folder in your local machine .
You could choose to use volumes as well , I guess

The the docker-compose-builder needs a mechanism to deploy smart contracts as well.
The easiest way would be to add a flag through which we can speficy a a metamask private key . Currently it picks up the key from a folder in your local machine .
You could choose to use volumes as well , I guess

Let's talk about this Monday, I'm not 100% sure how that is supposed to work but I can definitely accommodate it once I understand.

The the docker-compose-builder needs a mechanism to deploy smart contracts as well.
The easiest way would be to add a flag through which we can speficy a a metamask private key . Currently it picks up the key from a folder in your local machine .
You could choose to use volumes as well , I guess

Let's talk about this Monday, If the devnet script can take this argument then I can just pass it through from the CLI.

No the devnet script would need to be modifed a bit to take the argument .

found a bug, maybe only me.

python dockernet init --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin --protocol_path $OLROOT/protocol
python dockernet start --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin
python dockernet stop
python dockernet start --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin
docker ps and there will be only one container running, which is the builder
python dockernet start --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin
this time the building binary time will be noticeable(almost instant at step 4)
docker ps and the containers will show up correctly

found a bug, maybe only me.
1. `python dockernet init --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin --protocol_path $OLROOT/protocol`

2. `python dockernet start --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin`

3. `python dockernet stop`

4. `python dockernet start --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin`

5. `docker ps` and there will be only one container running, which is the builder

6. `python dockernet start --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin`
   this time the building binary time will be noticeable(almost instant at step 4)

7. `docker ps` and the containers will show up correctly

Sounds like the builder needed more time before the nodes can start. Does this happen every time for you? The way it currently works is that the script waits until the node folders were created before starting up all the nodes. This doesn't seem to happen for me but I'm running on ubuntu and my compile time is about 30 - 40 seconds.

found a bug, maybe only me.
1. `python dockernet init --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin --protocol_path $OLROOT/protocol`

2. `python dockernet start --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin`

3. `python dockernet stop`

4. `python dockernet start --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin`

5. `docker ps` and there will be only one container running, which is the builder

6. `python dockernet start --docker_path $OLDATA/dockertest --docker_bin $OLDATA/dockerbin`
   this time the building binary time will be noticeable(almost instant at step 4)

7. `docker ps` and the containers will show up correctly

Sounds like the builder needed more time before the nodes can start. Does this happen every time for you? The way it currently works is that the script waits until the node folders were created before starting up all the nodes. This doesn't seem to happen for me but I'm running on ubuntu and my compile time is about 30 - 40 seconds. It can also be that the builder didn't get killed when you ran the 'Stop' command.

yeah, every time. as below:


Issue using this lib with Travis-CI

Hey there, we use this library in our project but we have some troubles integrating it in Travis-CI, this is the  script
language: go

go:
  - 1.8.x
  - master

os:
  - linux
dist: trusty
addons:
        apt:
                packages:
                        libusb-1.0-0-dev
                        libusb-1.0-0
install:
  - go get -v github.com/gotmc/libusb
  - go build

script:
  - go tool vet -v -all ./

The error is
could not determine kind of name for C.LIBUSB_TRANSFER_TYPE_BULK_STREAM

@Nhoya Are you able to provide more details about the error?

Hi @matthewankin,
Thanks for the reply,the issue is relative to
go get -v github.com/gotmc/libusb
i'm actually unable to u

Closed by misclick

Any news? you tried to reproduce it?

Based on your .travis.yml file, you're trying to use the Trusty beta Build Environment. Looking at the whitelisted apt packages, libusb-1.0-0.dev and libusb-1.0-0 are not  included in the Trusty environment but are included in the Precise environment.

Have you tried using the Precise environment?
Have you tried using a sudo-enbaled environment instead of a container-based environment?

From the feedback you're providing, it seems you agree that the problem is not with the libusb library, but instead is a Travis-CI configuration issue.

Just to confirm that it's not a libusb problem, let me update the .travis.yml configuration to include both Linux and OS X and see what happens.

Yes, we tried Precise environment and still fails..
Seems your build fails too
github.com/gotmc/libusb
could not determine kind of name for C.LIBUSB_LOG_LEVEL_DEBUG
could not determine kind of name for C.LIBUSB_LOG_LEVEL_ERROR
could not determine kind of name for C.LIBUSB_LOG_LEVEL_INFO
could not determine kind of name for C.LIBUSB_LOG_LEVEL_NONE
could not determine kind of name for C.LIBUSB_LOG_LEVEL_WARNING
FAIL	github.com/gotmc/libusb [build failed]
# github.com/gotmc/libusb
could not determine kind of name for C.LIBUSB_LOG_LEVEL_DEBUG
could not determine kind of name for C.LIBUSB_LOG_LEVEL_ERROR
could not determine kind of name for C.LIBUSB_LOG_LEVEL_INFO
could not determine kind of name for C.LIBUSB_LOG_LEVEL_NONE
could not determine kind of name for C.LIBUSB_LOG_LEVEL_WARNING

It appears the issue is that Ubuntu Precise installs the C libusb 1.0.9, whereas [libusb][] expects a newer version of the C libusb.

I can confirm the problem is with the version of libusb installed by Ubuntu. What version of libusb are you running in production? You should be able to use pkg-config --modversion libusb-1.0 to determine.

1.0.21

On Travis using xenial the output of pkg-config --modversion libusb-1.0 is 1.0.9-rc3

It appears the problem is that the Go libusb required a newer version of C libusb than what was installed by Ubuntu 14.04 Trusty or 12.04 Precise. As a compromise, I've removed the reference to LIBUSB_BULK_STREAM_TRANSFER so that the Go libusb tests pass using the C libusb 1.0.17, which is what Ubuntu 14.04 Trusty install.
To get this to work, you'll need to make sure your Travis-CI configuration does not use Ubuntu 12.02 Precise, or you'll need to build a newer version of C libusb from source.
Versions of C libusb installed

Homebrew on OS X: 1.0.21
apt-get on Debian Jessie: 1.0.19
apt-get on Ubuntu 14.04 LTS Trusty: 1.0.17
apt-get on Ubuntu 12.02 LTS Precise: 1.0.9


Landing page

Description
Finished a basic landing page for this application
Fixes # (issue)
No issue, adding new page.
Type of change
Adding page
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[x] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

Closing till tests configured


Consider removing WebTestFramework reference from NuGetGallery.FunctionalTests.Core

I used to be able to run functional tests in VS2017 by just unloading the WebUITest projects.
Now I have to comment out all the WebUITest code in FunctionalTests.Core as well, or run in earlier version of VS.

Closing due to priority of refactoring work


Added lib/.gitkeep

Thanx. I added lib/ directory with .gitkeep file inside in my local branch. Will be reflected at the next pushing.


Add a note on adding complex64/128 in a future version

This also cleans up all the notes in the Data Types section, which were a bit messy and had some duplication.
And it introduces a new "Future extension" admonition, which uses the MyST "colon fence" (requires a newer version of MyST):

Closes gh-102

Thanks Leo, that sounds fine to me - I committed your suggestion and will add the diagram later this week.

Thanks Leo, that sounds fine to me - I committed your suggestion and will add the diagram later this week.

Updated to:

Updated to:

I think the figure mistakenly mentions complex32/64, which should be complex64/128

argh. fixed now:

Will do something about font sizes whenever we get back to really adding complex dtypes, can't be bothered with resizing all those circles for a slightly more uniform look now.

I think the figure mistakenly mentions complex32/64, which should be complex64/128

argh. fixed now:

Will do something about font sizes whenever we get back to really adding complex dtypes, can't be bothered with resizing all those circles for a slightly more uniform look now.

Done. Thanks for reviewing!

Done. Thanks for reviewing!


Docker problems: time zone specification via env var?

I'm using the vanilla single-threaded Huginn docker image from Docker Hub. Since version (7c90b83734a4ac1b6605f722d202e692a7c7b851), it fails to start up with this error:
/tmp/.env: line 10: syntax error near unexpected token ')'
I've got it set up to start up by running /scripts/init (which generates the .env) then bin/threaded.rb.
Do you know if there was a change in that hash ("2 months ago", according to Docker Hub) that might cause that? My suspicion is that the issue may be in specifying the time zone (as an env var) Eastern Time (US & Canada) in my case. It used to work with the same settings with 9cd2f565ec1c702b56bec696e2b487886dba1f63 and prior.

Can you share the command or compose file you use to start the container?
docker run -e TIMEZONE="Eastern Time (US & Canada)"  huginn/huginn works for me

This is running on Amazon ECS, so there is no docker command. I don't specify a command beyond the default in the Dockerfile.
Did the commit https://github.com/huginn/huginn/commit/46e7a675c78037cabc67532e19d64eb00ef2b7b4 dramatically change how environment variables, specifically the database password, are passed into Huginn? Is it possible that this change is causing the problem? (I'm now noticing that one of my database passwords has a closing parenthesis in it, and that may be the problem instead of the timezone?)

This is probably the part that causes your issue. The change was supposed to fix issues with variables passed in via a .env file that are not quoted but need to be.
Do you know how ECS passes in the environment variables you specify? I tried a bunch of variations but was not able to reproduce your problem.

In ECS's JSON it looks like this.
 {           "name": "TIMEZONE",           "value": "\"Eastern Time (US & Canada)\""         },
In my deploy script (which creates the JSON above) it looks like this:        \"environment\": [ { \"name\" : \"TIMEZONE\", \"value\" : \"\\\"Eastern Time (US & Canada)\\\"\" }, ]

I think I've fixed the parenthesis problem. Just removing all the escapes and extra quotes works fine with latest.     { \"name\" : \"TIMEZONE\", \"value\" : \"Eastern Time (US & Canada)\" },
However, one password also has an equals sign in it. That doesn't work. The password that gets passed through to Rails (via the .env file) is truncated at the equals sign. (E.g. pa)ss=word shows up just as pa)ss) Having trouble trying to escape that in a way that works -- since we know that quoting doesn't work with the parenthesis.

I think I've fixed the parenthesis problem. Just removing all the escapes and extra quotes works fine with latest.  { \"name\" : \"TIMEZONE\", \"value\" : \"Eastern Time (US & Canada)\" },

Interesting, ECS must do some escaping themselves with the variables you are passing in, probably to ensure the quotes are preserved. In that case not double quoting the string looks correct to me.

Having trouble trying to escape that in a way that works -- since we know that quoting doesn't work with the parenthesis.

I also can not get that to work. Quoting the = does not seem to do anything, it either fails to parse the variable or it is truncated at the =.
Did the same password work before https://github.com/huginn/huginn/commit/46e7a675c78037cabc67532e19d64eb00ef2b7b4?
@baip Do you have an idea how we can fix this?

I think it's the line IFS="=" that causes Bash to split words at the = symbol. I just created a small patch that should now handle variables containing = (as well as whitespace etc.) correctly.

I'm trying to pass "TIMEZONE=Europe/Copenhagen". Doing so, an event won't run.
I tried to pass "Copenhagen" only and, despite the event runs it won't propagate.
What's the right way of passing such a timezone?

@baip Would you mind sharing your patch, maybe with a pull request? I have similar issues and would appreciate a fixed huginn version :-)


bug: kcp workload sync command does not work with EKS/AKS/GKE clusters

Describe the bug
I have Installed KCP in my EKS cluster with the following version details:
Client Version: v1.25.5
Kustomize Version: v4.5.7
Server Version: v1.24.3+kcp-v0.11.0
After installing, when I am executing the "kubectl kcp workload sync kind --syncer-image ghcr.io/kcp-dev/kcp/syncer:v0.10.0 -o syncer-kind-main.yaml" command in my eks/aks/gke cluster, initially the syncer pod shows that its in running state but after a while its going into error state and the syncer pod is unable to connect to the kind cluster. Also, I can notice that it is looking for kind cluster instead of EKS/AKS/GKE cluster.
ERROR in syncer pod:
I0711 10:03:17.781845 1 syncer.go:83] "syncing" resource-types=[]
I0711 10:03:17.783302 1 syncer.go:79] "starting syncer" syncTarget.workspace="1b3sbf8cq5r4epjn" syncTarget.name="kind"
I0711 10:03:17.783726 1 syncer.go:106] "attempting to retrieve the Syncer virtual workspace URL" syncTarget.workspace="1b3sbf8cq5r4epjn" syncTarget.name="kind"
E0711 10:03:47.785391 1 run.go:74] "command failed" err="Get `\"[https://17********/clusters/1b3sbf8cq5r4epjn/apis/workload.kcp.dev/v1alpha1/synctargets/kind\":]` dial tcp 17********: i/o timeout"

So is there a way I can run the syncer with EKS/AKS/GKE instead of kind cluster?
Steps To Reproduce

Create the eks/aks/gke cluster
Install kcp
Add Syncer

Expected Behaviour
The syncer should be added properly and the syncer pod should be in running state in eks/aks/gke cluster
Additional Context
No response

I believe the syncer is installed in the EKS/GKE/AKS cluster, which would indicate its running as a pod on the worker nodes. Going by the error message https://17********/ , the pod is trying to connect to a vpc local address, is that true? I believe there is plumbing missing that does not allow the pod connectivity to 172.**

/transfer-issue contrib-tmc

/transfer contrib-tmc

/transfer-issue contrib-tmc

/transfer-issue contrib-tmc

/transfer-issue contrib-tmc


Generate different UUID in Content Tree

Same UUID in Content trees result in misbehavior.  Randomize UUID and ensure they are different for different entities in config.

Fixed


feat: plot matching sprite func

This PR adds functionality to show matching images in a sprite. The leftmost is the query followed by matching results. There is a gap between the query and its matches to distinguish/differentiate.

@makram93 mybad, literal only works on py3.8+, please ignore my first 2 comments.


[SPARK-17107][SQL] Remove redundant pushdown rule for Union

What changes were proposed in this pull request?
The Optimizer rules PushThroughSetOperations and PushDownPredicate have a redundant rule to push down Filter through Union. We should remove it.
How was this patch tested?
Jenkins tests.

Test build #63919 has started for PR 14687 at commit a4c015d.

Test build #63919 has finished for PR 14687 at commit a4c015d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63919/
Test PASSed.

This seems fair. I am I right to say that PushThroughSetOperations only remaining functionality is to push a project through a Union? We could rename it to reflect this a little better.

@hvanhovell Thanks for review. I renamed PushThroughSetOperations to PushProjectionThroughUnion.

Test build #63965 has started for PR 14687 at commit f840ccb.

Test build #63965 has finished for PR 14687 at commit f840ccb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63965/
Test PASSed.

LGTM. Merging to master. Thanks!


Enable ca signed kubelet server certs

Hey guys,
This PR builds on https://github.com/digitalrebar/provision-content/pull/293 - I discovered that on a kubeadm installation, the kubelets serve their API using self-signed certificates, which prevents metrics-server from working in a secure way.
(Details at https://github.com/kubernetes/kubeadm/issues/1223)
This PR enables the optional addition of serverTLSBootstrap to kubeadm.cfg, to force the kubelets to seek CA-signed client and server certificates instead of the default behaviour (a self-signed server cert).
I've also added in the "kubelet rubber stamp" (https://github.com/kontena/kubelet-rubber-stamp) approver, to subsequently approve the pending kubelet server CSRs (server CSRs aren't auto-approved anymore)
All this magic is hidden behind a param krib/sign-kubelet-server-certs, which defaults to false.
Cheers!
D

Updated to [WIP] because I'm still waiting on the conclusion of this certmanager webhook issue for the nginx ingresses : https://github.com/jetstack/cert-manager/issues/1302

No longer a WIP because the front-proxy-ca bug is fixed (https://github.com/digitalrebar/provision-content/pull/296)


Helm chart does not support numTrustedProxies

Even though the format for the istio ingress helm values is the same as what one would create to set meshConfig.defaultConfig.gatewayTopology.numTrustedProxies, it is completely incapable of setting those values, since it ignores the existence of gatewayTopology in the templating stage.
https://github.com/istio/istio/blob/master/manifests/charts/gateways/istio-ingress/values.yaml#L312
The only way to do this shouldn't be altering the deployment itself, the documentation says that this process should be the same as istioctl or the Operator (citing https://istio.io/latest/docs/setup/install/helm/)

I am not suggesting its not confusing at all, but the way to do it is to configure it on the istio-control chart. Note if your ingress gw is not in the same namespace, you MUST use https://istio.io/latest/docs/setup/additional-setup/gateway/ method for it to work.

I'd like to place a correction here that the easiest way to do it without actual support is to directly annotate. Here's the structure:
gateways:
  istio-ingressgateway:
    podAnnotations:
      proxy.istio.io/config: '{"gatewayTopology" : { "numTrustedProxies": 1}}'


[Request for External] Codeunit 11 "Gen. Jnl.-Check Line" - CheckGenProdPostingGroupWhenAdjustForPmtDisc,CheckBalGenProdPostingGroupWhenAdjustForPmtDisc

Hi, would it be possible to modify CheckGenProdPostingGroupWhenAdjustForPmtDisc and CheckBalGenProdPostingGroupWhenAdjustForPmtDisc in codeunit 11 from local to external?
Having the procedures CheckGenProdPostingGroupWhenAdjustForPmtDisc and CheckBalGenProdPostingGroupWhenAdjustForPmtDisc as an external would really help us.
Thanks

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


feat: Add warning for no api

This PR will close #380
Description
Added a check to the configuration file loading function that outputs a warning if it cannot find a section for datagateway or search api in the config file
Testing Instructions
Add a set up instructions describing how the reviewer should test the code

[ ] Review code
[ ] Check GitHub Actions build
[ ] If icatdb Generator Script Consistency Test CI job fails, is this because of a deliberate change made to the script to change generated data (which isn't actually a problem) or is here an underlying issue with the changes made?
[ ] Review changes to test coverage
[ ] Does this change mean a new patch, minor or major version should be made? If so, does one of the commit messages feature fix:, feat: or BREAKING CHANGE: so a release is automatically made via GitHub Actions upon merge?
[ ] {more steps here}

Agile Board Tracking
Connect to #380

Logging seems to output the message during startup as well. If I add a print statement then I see the message twice. See my console output below
[root@localhost datagateway-api]# poetry run python -m datagateway_api.src.main
   WARNING: There is no API specified in the configuration file
   WARNING: There is no API specified in the configuration file
 * Serving Flask app 'main' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off

Ah ok, I didn't notice that! Looks good then, I'll approve


How to incrementally add properties?

I'm creating a JsonSchema dynamically by code.
How can I add a property to the existing properties?
The following will produce a JsonSchema with only a "p2" property:
var b = new JsonSchemaBuilder();

b = b.Properties(("p1", new JsonSchemaBuilder().Type(SchemaValueType.Object)));
b = b.Properties(("p2", new JsonSchemaBuilder().Type(SchemaValueType.Object)));

Interesting. This is a case I hadn't considered.
I can update those methods to add the new values to the current set in the builder.

I can't find a way to do this that I want to add to the library.
The idea is behind the current design is that a schema should be immutable once it's built.  That said, I understand the argument that the builder shouldn't be immutable, but your use isn't quite what I had expected.
My suggestion would be to store your collection of properties in a dictionary separately and then pass that to the builder:
var builder = new JsonSchemaBuilder();
var propertySchemas = new Dictionary<string, JsonSchema>();
foreach(var prop in propertiesToGenerate)
{
    var propertySchema = BuildFromProperty(prop); // whatever you're doing to generate a schema
    propertySchemas[prop.Name] = propertySchema;
}
builder.Properties(propertySchemas);

Aside from that, I've create a gist for what I have currently.  It does require that I update the builder to include a new Get<T>() method (which I'll publish), but they're just extension methods, so you should be able to just use as is and/or create your own.

My suggestion would be to store your collection of properties in a dictionary separately and then pass that to the builder:

Yes, that's the path I took.
Thank you for your input.

The idea is behind the current design is that a schema should be immutable once it's built.

Yes, I saw the pattern.

Aside from that, I've create a gist for what I have currently.

Looks good.
Not sure if you need it, but here's another idea: what if the Properties() method took a 'generator'? For example:
builder.Properties(() => // return properties by some custom way);


Put full build

[x] I read the conda-forge documentation and could not find the solution for my problem there.

Issue: Currently, this build is working for OSX on CPU, and needs to be extended for Linux and Windows using CPU and GPU.

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Tracking this here: https://github.com/sarthakpati/torch-scatter-feedstock/tree/full_build

@jaimergp may have some insight into what's going wrong here.

Thanks, any help on this will be greatly appreciated!

There are no pytorch builds for Windows AFAIK, so for now we can only do Linux builds.

This is done. Thanks a ton to @hmaarrfk and @jaimergp!


LAB_AK_01_Implementing_identity_services_and_Group_Policy.md

Source:
'Lab answer key:
Current Translation:
实验室答案：
Suggested Translation:
'实验室解答：

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Fixed

Current Translation:
'实验室解答：
Suggested Translation:
实验室解答：

Not fixed yet.

Fixed

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team


Tagging bucket issue

Fixed the TagNameSpace Issue.
Fixed the Bucket Rotation Issue.
Added Variable to support External Vault.

Tagging and bucket fixes look ok, but I don't see any of the actual code for the external vault feature (https://github.com/oracle-quickstart/oci-landing-zones/compare/integration...DragonDM:oci-landing-zones:external_vault) here, just the variable definitions.  Missed git merge?


Package for Solus Linux

It would be good if VSCode could be packaged for Solus. Currently, the OSS version is used, but that introduces a few quirks that would be nicer to not have to deal with.
Solus is currently #8 on distrowatch so while it may no be the biggest out there, it is definately popular.

Unfortunately we can't tackle them all. This is why we make a ZIP download available.


"Error displaying widget: model not found" in notebook launched in Jupyter Lab

Greetings--
I have had success running the demo code in a jupyter notebook launched via jupyter notebook. However, the very same demo code (in the exact same notebook that worked before!) fails when attempting to render the report when launched within Jupyter Lab.  In place of rendering the embedded report, the cell instead outputs this generic Jupyter widget-fail message: "Error displaying widget: model not found"
I have followed the special installation instructions provided in the README for Jupyter Lab both in existing and brand new conda environments. In the Jupyter Lab UI, the extension shows as being installed and activated. The txt file attached documents a "fresh" conda environment with the package and lab extensions installed and jupyter lab successfully built, but where I'm still seeing the error. I'm working in a relatively new and updated Windows 10 environment.
Love this package! . . . and hope you can help me get it to run in Jupyter Lab. Thank you!
Steve
pbi_env.txt

I have the same issue

Same issue here. Hope it could be solved soon. The package would be really helpful. Thank you!

+1

+1

Hi everyone,
After some investigation, we found that this issue is not related to our package, rather the package manager conda.
Here are couple of solutions to resolve it-

Create a new virtual environment with conda

conda create --name envname
Install the required libraries (powerbiclient, jupyterlab, ipywidgets, ...)
Run the jupyterlab

Update conda dependencies

conda uninstall jupyterlab
conda install -c conda-forge jupyterlab jupyterlab_widgets ipywidgets
Run the jupyterlab

For either of them, ensure you have these extensions enabled-


feat: rexport-rules

https://github.com/antfu/eslint-define-config#1-re-export-rules-for-each-plugin

This would be the most straightforward way (current)

import { VueRules } from 'eslint-define-config'

But ideally I would think it's better to expose as a sub modules

import { defineConfig } from 'eslint-define-config'
import { VueRules, VitestRules } from 'eslint-define-config/rules'

Or maybe even:

import { defineConfig } from 'eslint-define-config'
import { Plugins } from 'eslint-define-config/rules'

const VueRules = Plugins['eslint-plugin-vue'] // Very explicit for each package.

I can update the PR based on your preference.

I would like to immediately jump to the @eslint-type/*, because that way I wont introduce an already planned breaking change

the @eslint-type/* monorepo is working now
so can we close this PR?


Our VS Code settings aren't in the repo

We need to save ~/Library/Application Support/Code/User/settings.json.

Ultimately, the official Settings Sync is probably the way to go, but we will forge ahead to learn more about Dotfiles.


Add option to force use MockDatastore

Useful for testing or if you have a free admin game.
For example on free Admin games (or other games too) you never wan't any datastores to ever save.

finally, mds.

I have experienced this within a game I moderate as well. It carries across multiple games, as both of them use adonis and I haven't been able to keep or even remove admins since about 4 days ago.

@Expertcoderz someone said that the DataStore was working fine until 4 days ago. Could this maybe have caused the issue somehow?
Because people that use :mod, it apparently doesn't save across the other servers. And any server, even new created ones.

No. Unless this warn(":: Adonis :: Using MockDataStoreService instead of DataStoreService") appears in the console. There is no other way the datastore could be local

It surely can't be this pull request. The only it could be this pull request if the settings settings.LocalDatastore is set to true

But there have been a lot of other recent pull requests that also affect the datastores & admin loading so it could have something to do with those

It surely can't be this pull request. The only way it could be this pull request would be if the settings settings.LocalDatastore is set to true.

what's the default value of the setting?

But there have been a lot of other recent pull requests that also affect the datastores & admin loading so it could have something to do with those

we need to find which one :shrug:

disregard I am about to find the issue
it wasn't caused by this push request


Added missing module: xtend

Fixes #298

Beat me to it, cheers!

No problem.
Greenkeeper notifies me when things break :)


[enhancement] Use array in @post hooks

I have instances where I want to achieve the same thing using different hooks but just end up having to duplicate the code, would it be possible or be a good idea to allow an array of hooks to do the same thing?
Currently:
      @Post<Contact>('save', (data) => addNotePost(data, Entities.CONTACT))
      @Post<Contact>('findOneAndUpdate', (data) => addNotePost(data, Entities.CONTACT))

Enhancement:
      @Post<Contact>(['save', 'findOneAndUpdate'], (data) => addNotePost(data,
       Entities.CONTACT))

i think this is not within the scope of typegoose, but you could make a simple function like below:
function hookwrapper(next: () => void) {
    return addNotePost(next, Entities.CONTACT);
}

@Post<Contact>("save", hookwrapper)
@Post<Contact>("findOneAndUpdate", hookwrapper)

Note: this should work, but somehow i found that "save" and many others are not declared right (only "count" and "insertMany" are declared)

@Ben305 this can be closed because it is included in v6.0.0


How to connect the output of "Tune model hyperparameters"?

There are 2 outputs to this step.
There is no documentation what the 2 outputs are.
By drag and drop, it seems that the left output is the data - which data?  Validation set or the Training set?
The right output seems to be the selected model.
The right output (model) then connects to the left input of model evaluation?
So then it crosses?
Not very intuituve....

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d1b9d373-2140-ead0-e1b2-de63f8e94125
Version Independent ID: 0bcd0103-042c-0ed8-2c8b-922ee27bff3c
Content: Tune Model Hyperparameters - Azure Machine Learning
Content Source: articles/machine-learning/algorithm-module-reference/tune-model-hyperparameters.md
Service: machine-learning
Sub-service: core
GitHub Login: @likebupt
Microsoft Alias: keli19

@hermandr Thanks for the feedback. We are looking into this and will get back to you soon.

@likebupt, can you assist?

Hi @hermandr  ,
Thanks for your feedback.
You could hover on the port and the port name will show up like following:

The left port is sweep result, right-click and you could visualize the sweeping parameters and the metrics.
The right port is the Trained best model, which could be used to score.
You can also find a sample of this module in the homepage of Designer,

@hermandr We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Thank you, it's working and clear explanation.
Would be great if documentation was clearer.

@hermandr Yes, We created the backlog item for documentation update. We will update with PR once it's completed.


add extension block for 1099ltc, 1099q, 1099r, 1099s, 1099sa, 1099sb

Codecov Report

Merging #40 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #40   +/-   ##
=======================================
  Coverage   80.97%   80.97%
=======================================
  Files          15       15
  Lines        1130     1130
=======================================
  Hits          915      915
  Misses        127      127
  Partials       88       88

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f2c20f9...3467cdb. Read the comment docs.


Add qiskit-ibm-runtime as ibm_extra in qiskit metapackage

What is the expected feature or enhancement?
Add an "ibm" section, an ibm_extra list here and add qiskit-ibm-runtime to the list.
Add ibm_extra to the "all" section as well.
Acceptance criteria
Both below commands should install qiskit-ibm-runtime
pip install qiskit[ibm]
pip install qiskit[all]

Don't think Qiskit team is ok adding this, see comments in linked PR, closing, will reopen if needed.


[halide] Fix can't be found by cmake.

Related issue: #8782
All features test failed on master, this has nothing to do with my change.

/azp run

/azp run

/azp run


Add initial documentation for benchcomp

This commit adds a front page summary including quick start, as well as a description of benchcomp's command line and how it works. This should help users get started. Documentation generated from the code schemas for the config file, visualizations, and parsers will follow this commit.

How is this change tested?

Is this a refactor change?

Checklist

[x] Each commit message has a non-empty body, explaining why the change was made
[ ] Methods or procedures are documented
[ ] Regression or unit tests are included, or existing tests cover the modified code
[x] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Here is the generated version of the graphviz diagram:

Can you add a link to the rendered version of the docs?

AFAICT the rendered documentation isn't hosted anywhere until this gets merged? I sent you a tarball offline.