ML | Machine Learning Algorithms | Machine Learning library

It looks like setuptools>=58 breaks support for use_2to3:

setuptools changelog for v58

So you should update setuptools to setuptools<58 or avoid using packages with use_2to3 in the setup parameters.

I was having the same problem, pip==19.3.1

When started, MailboxProcessor will run the asynchronous computation specified as the body. It will continue running until the body finishes (either by reaching the end or by throwing an exception) or until the program itself is terminated (as the mailbox processor runs in the background).

To comment on your examples:

• This mailbox processor prints nothing and halts the program - I assume you run this in a console app that terminates after the mailbox processor is created. There is nothing blocking the program and so it ends (killing the mailbox processor in the background).

• This mailbox processor counts up to 2207 then the program exits - I suspect this is for the same reason - your program creates the mailbox processor, which manages to run for a while, but then the program itself is terminated and the mailbox processor killed.

• This mailbox processor prints 1 then the program exits - The body of the mailbox processor hangs and the next two messages are queued. The queue is never processed (because the body has hanged) and then your program terminates.

You will get more useful insights if you add something like Console.ReadLine() to the end of your program, because this will prevent the program from terminating and killing the mailbox processor.

For example, the following will process all 100000 items:

This happens, during the ground-truth-merge job, when the spark can't find any data either in '/opt/ml/processing/groundtruth/' or '/opt/ml/processing/input_data/' directories. And that can happen when either you haven't sent any requests to the sagemaker endpoint or there are no ground truths.

I got this error because, the folder /opt/ml/processing/input_data/ of the docker volume mapped to the monitoring container had no data to process. And that happened because, the thing that facilitates entire process, including fetching data couldn't find any in S3. and that happened because, there was an extra slash(/) in the directory to which endpoint's captured-data will be saved. to elaborate, while creating the endpoint, I had mentioned the directory as s3:////, while it should have just been s3:///. so, while the thing that copies data from S3 to docker volume tried to fetch data of that hour, the directory it tried to extract the data from was s3://////////(notice the two slashes). So, when I created the endpoint-configuration again with the slash removed in S3 directory, this error wasn't present and ground-truth-merge operation was successful as part of model-quality-monitoring.

I am answering this question because, someone read the question and upvoted it. meaning, someone else has faced this problem too. so, I have mentioned what worked for me. And I wrote this, so that StackExchange doesn't think I am spamming the forum with questions.

$event is not the same type as SortEvent, as you need. $event will always contain a lot of key-value pairs, unless you are using with anything other than legacy elements.

In the first case, the type of l is unified with the type defined in the module M, which defines the module type. Since the type is introduced after the value l, which is a parameter in an eager language so it already exists, the value l receives a type that doesn't yet exist at the time of its creation. It is the soundness requirement of the OCaml type system that the value lifetime has to be enclosed with its type lifetime, or more simply each value must have a type. The simplest example is,

This is a known bug. I am following up with product group to see if there any update for this bug. For the workaround you mentioned, it need you to go to the node failing with the JobConfigurationMaxSizeExceeded exception and manually set AZUREML_COMPUTE_USE_COMMON_RUNTIME:false in their Environment JSON field.

The node is as below screenshot.

Yes, it's just an if-expression:

Encountered the same problem. Update Huawei services. Please take care. Remember to keep your dependencies on the most up-to-date version. This problem is happening on Merged-Manifest.

The issue is that the 'a type variable in the (l': 'a t) annotation lives in the whole toplevel definition and thus outlives the polymorphic annotation.

In order to illustrate this scope issue for type variables, consider