tzlocal | Python module that tries to figure

I reverted back to Xorg from wayland and its working, no more warnings

Here are the steps:

1. Disbled Wayland by uncommenting WaylandEnable=false in the /etc/gdm3/custom.conf
2. Add QT_QPA_PLATFORM=xcb in /etc/environment
3. Check whether you are on Wayland or Xorg using:

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.

You have to pass function to add_job but instead of it you passed returned value of the trigger.UpdateSetRefresh.
So correct statement would be like:

Actually it was a really simple solution that I didn't notice a paremeter from apscheduler which is explained in the documentation as:

misfire_grace_time (int) – the time (in seconds) how much this job’s execution is allowed to be late (None means “allow the job to run no matter how late it is”)

So I added this parameter to my scheduler as below:

Consider creating a separate environment, e.g.,

In Django, the gettext_lazy(…) function [Django-doc] is often imported as _ to manage translations. This is explained in the Standard translation:

Python’s standard library gettext module installs _() into the global namespace, as an alias for gettext(). In Django, we have chosen not to follow this practice, for a couple of reasons

(…)

Because of how xgettext (used by makemessages) works, only functions that take a single string argument can be imported as _:

• gettext()
• gettext_lazy()

You thus should add:

Since you are using Django 2.2, your Middleware class must accept a get_response argument:

you should define your class like this.

I guess that what you want is health of instances in the cluster. If so you have to list_instances, and there you can find their Status. You can also iterate over the instance ids from the previous command and use describe_instance_status for more details.

Streamlit share runs the app in a linux environment meaning there is no pywin32 because this is for windows.

Delete the pywin32 from the requirements file and also the pywinpty==1.1.6 for the same reason.

After deleting these requirements re-deploy your app and it will work.